System and method of block chain based protection for customized data integration processes

ABSTRACT

A method of block chain based data protection may comprise receiving a user block chain instruction to record a address-identified memory location at which a dataset field value containing sensitive personal information is stored pursuant to a customized data integration process modeled via a graphical user interface, creating a block chain associated with the dataset field value, receiving an identification of the address-identified memory location from a customized data integration process remote execution location, and creating a first block storing the identification of the address-identified memory location within the block chain. The method may further comprise receiving a user deletion instruction to delete the dataset field value from the address-identified memory location, automatically generating a runtime engine and machine executable deletion code instructions for deletion of the dataset field value from the address-identified memory location, and transmitting the runtime engine and the machine executable deletion code instructions for execution at the remote execution location.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to a system and method fordeploying and executing customized data integration processes. Morespecifically, the present disclosure relates to identification andtracking of personally identifying datasets via block chain as they aremanipulated during a customized data integration process.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, calculate, determine, classify, process, transmit, receive,retrieve, originate, switch, store, display, communicate, manifest,detect, record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer (e.g., desktop or laptop), tablet computer, mobile device(e.g., personal digital assistant (PDA) or smart phone), a head-mounteddisplay device, server (e.g., blade server or rack server), a networkstorage device, a network storage device, a switch router or othernetwork communication device, other consumer electronic devices, or anyother suitable device and may vary in size, shape, performance,functionality, and price. The information handling system may includerandom access memory (RAM), one or more processing resources such as acentral processing unit (CPU) or hardware or software control logic,ROM, and/or other types of nonvolatile memory. Additional components ofthe information handling system may include one or more disk drives, oneor more network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse,touchscreen and/or a video display. The information handling system mayalso include one or more buses operable to transmit communicationsbetween the various hardware components. Further, the informationhandling system may include telecommunication, network communication,and video communication capabilities and require communication among avariety of data formats.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will now be described by way of example withreference to the following drawings in which:

FIG. 1 is a block diagram illustrating an information handling systemaccording to an embodiment of the present disclosure;

FIG. 2 is a block diagram illustrating a simplified integration networkaccording to an embodiment of the present disclosure;

FIG. 3A is a graphical diagram illustrating a user-generated flowdiagram of a customized data integration process according to anembodiment of the present disclosure;

FIG. 3B is a graphical diagram illustrating a user-generated flowdiagram of a deletion process for electronic data records according toan embodiment of the present disclosure;

FIG. 4 is a block diagram illustrating a block chain module storingmetadata tracking block chains according to an embodiment of the presentdisclosure;

FIG. 5 is a block diagram illustrating a master data management modulefor tracking storage and manipulation of a user-specified dataset fieldvalue according to an embodiment of the present disclosure;

FIG. 6 is a block diagram illustrating a data integration processingmodule for reporting physical storage locations of a dataset field valuepursuant to one or more executed integration processes according to anembodiment of the present disclosure;

FIG. 7 is a block diagram illustrating a master data management modulefor automatic deletion of a dataset field value from one or more storagelocations according to an embodiment of the present disclosure;

FIG. 8 is a flow diagram illustrating a method of creating a block chaindescribing physical storage locations for a dataset field valueaccording to an embodiment of the present disclosure; and

FIG. 9 is a flow diagram illustrating a method of reporting metadata foruser-identified datasets transmitted according to a customized dataintegration process according to an embodiment of the presentdisclosure.

The use of the same reference symbols in different drawings may indicatesimilar or identical items.

DETAILED DESCRIPTION

The following description in combination with the Figures is provided toassist in understanding the teachings disclosed herein. The descriptionis focused on specific implementations and embodiments of the teachings,and is provided to assist in describing the teachings. This focus shouldnot be interpreted as a limitation on the scope or applicability of theteachings.

Conventional software development and distribution models have involveddevelopment of an executable software application, and distribution of acomputer-readable medium, or distribution via download of theapplication from the worldwide web to an end user. Upon receipt of thedownloaded application, the end user executes installation files toinstall the executable software application on the user's personalcomputer (PC), or other information handling system. When the softwareis initially executed, the application may be furtherconfigured/customized to recognize or accept input relating to aspectsof the user's PC, network, etc., to provide a software application thatis customized for a particular user's computing system. This simple,traditional approach has been used in a variety of contexts, withsoftware for performing a broad range of different functionality. Whilethis model might sometimes be satisfactory for individual end users, itis undesirable in sophisticated computing environments.

Today, most corporations or other enterprises have sophisticatedcomputing systems that are used both for internal operations, and forcommunicating outside the enterprise's network. Much of present dayinformation exchange is conducted electronically, via communicationsnetworks, both internally to the enterprise, and among enterprises.Accordingly, it is often desirable or necessary to exchangeinformation/data between distinctly different computing systems,computer networks, software applications, etc. In many instances, thesedisparate computing networks, enterprises, or systems are located in avariety of different countries around the world. The enabling ofcommunications between diverse systems/networks/applications inconnection with the conducting of business processes is often referredto as “business process integration.” In the business processintegration context, there is a significant need to communicate betweendifferent software applications/systems within a single computingnetwork, e.g. between an enterprise's information warehouse managementsystem and the same enterprise's purchase order processing system. Thereis also a significant need to communicate between different softwareapplications/systems within different computing networks, e.g. between abuyer's purchase order processing system, and a seller's invoicingsystem. Some of these different software applications/systems may becloud-based, with physical servers located in several differentcountries, cities, or other geographical locations around the world. Asdata is integrated between and among these cloud-based platforms,datasets may be stored (e.g., temporarily or indefinitely) in some format physical servers in these various geographical locations.

Relatively recently, systems have been established to enable exchange ofdata via the Internet, e.g. via web-based interfaces forbusiness-to-business and business-to-consumer transactions. For example,a buyer may operate a PC to connect to a seller's website to providemanual data input to a web interface of the seller's computing system,or in higher volume environments, a buyer may use an executable softwareapplication known as EDI Software, or Business-to-Business IntegrationSoftware to connect to the seller's computing system and to deliverelectronically a business “document,” such as a purchase order, withoutrequiring human intervention to manually enter the data. Such softwareapplications are available in the market today. These applications aretypically purchased from software vendors and installed on acomputerized system owned and maintained by the business, in thisexample, the buyer. The seller will have a similar/complementarysoftware application on its system, so that the information exchange maybe completely automated in both directions. In contrast to the presentdisclosure, these applications are purchased, installed and operated onthe user's local system. Thus, the user typically owns and maintains itsown copy of the system, and configures the application locally toconnect with its trading partners.

In both the traditional and more recent approaches, the executablesoftware application is universal or “generic” as to all tradingpartners before it is received and installed within a specificenterprise's computing network. In other words, it is delivered todifferent users/systems in identical, generic form. The softwareapplication is then installed within a specific enterprise's computingnetwork (which may include data centers, etc., physically locatedoutside of an enterprises' physical boundaries). After the genericapplication is installed, it is then configured and customized for aspecific trading partner, after which it is ready for execution toexchange data between the specific trading partner and the enterprise.For example, Walmart® may provide on its website specifications of howelectronic data such as Purchase Orders and Invoices must be formattedfor electronic data communication with Walmart®, and how that datashould be communicated with Walmart®. A supplier/enterprise is thenresponsible for finding a generic, commercially available softwareproduct that will comply with these communication requirements andconfiguring it appropriately. Accordingly, the software application willnot be customized for any specific supplier until after that supplierdownloads the software application to its computing network andconfigures the software application for the specific supplier'scomputing network, etc. Alternatively, the supplier may engage computerprogrammers to create a customized data integration process orcustomized software application to meet these requirements, which isoften exceptionally time-consuming and expensive.

Recently, systems and software applications have been established toprovide a system and method for on-demand creation of customized dataintegration processes or customized software applications in which thecustomization occurs outside of an enterprise's computing network. Thesesoftware applications and data processes are customized for a specificenterprise before they arrive within the enterprise's computing network,and are delivered to the destination network in customized form. TheDell Boomi® Application is an example of one such software application.With Dell Boomi® and other similar applications, an employee within anenterprise can connect to a website using a specially configuredgraphical user interface to visually model a customized data integrationprocess via a flowcharting process, using only a web browser interface.During such a modeling process, the user would select from apredetermined set of process-representing visual elements that arestored on a remote server, such as the web server. By way of an example,the customized data integration process could enable a bi-directionalexchange of data between internal applications of an enterprise, betweeninternal enterprise applications and external trading partners, orbetween internal enterprise applications and applications runningexternal to the enterprise.

An integration application management system in an embodiment may allowa user to create a customized data integration software application bymodeling a customized data integration process flow using a visual userinterface. A modeled customized data integration process flow inembodiments of the present disclosure may model actions taken on dataelements pursuant to executable customized data integration codeinstructions without displaying the code instructions themselves. Insuch a way, the visual user interface may allow a user to understand thehigh-level summary of what executable integration code instructionsachieve, without having to read or understand the customized dataintegration code instructions themselves. Similarly, by allowing a userto insert visual elements representing portions of a customized dataintegration process into the modeled customized data integration processflow displayed on the visual user interface, embodiments of the presentdisclosure allow a user to identify what she wants executable customizeddata integration code instructions to achieve without having to writesuch executable customized data integration code instructions.

Once a user has chosen what she wants an executable customized dataintegration code instruction to achieve in embodiments herein, thecustomized data integration code instructions capable of achieving sucha task may be generated. Code instructions for achieving a task can bewritten in any number of languages and/or adhere to any number ofstandards, often requiring a code writer to have extensive knowledge ofcomputer science and languages. The advent of open-standard formats forwriting code instructions that are both human-readable and machineexecutable have made the writing of code instructions accessible toindividuals that do not have a high level knowledge of computer science.Such open-standard, human-readable, data structure formats includeextensible markup language (XML) and JavaScript Object Notification(JSON). Because code instructions adhering to these open-standardformats are more easily understood by non-specialists, many companieshave moved to the use of code instructions adhering to these formats inconstructing their data repository structures and controlling the waysin which data in these repositories may be accessed by both internal andexternal agents. In order to execute code instructions for accessingdata at such a repository during a business integration process, thecustomized data integration code in some embodiments herein may bewritten in accordance with the same open-standard formats or otherknown, or later-developed standard formats.

In addition to the advent of open-standard, human-readable,machine-executable code instructions, the advent of applicationprogramming interfaces (APIs) designed using such open-standard codeinstructions have also streamlined the methods of communication betweenvarious software components. An API may operate to communicate with abackend application to identify an action to be taken on a dataset(e.g., a data field name and data field value, or name/value pair) thatthe backend application manages, or which is being transmitted formanagement to the backend application. Such an action and convention foridentifying the dataset or its location may vary among APIs and theirbackend applications. For example, datasets may be modeled according touser-supplied definitions. Each dataset may contain a user-defineddataset field name, which may describe a type of information. Eachuser-defined dataset field name may be associated with a dataset fieldvalue. In other words, datasets may be modeled using a field name/valuepairing. For example, a dataset for a customer named John Smith mayinclude a first dataset field name “f_name” paired with a first datasetfield value “John,” and a second dataset field name “l_name” paired witha second dataset field value “Smith.” A user in an embodiment may defineany number of such dataset field name/value pairs. Other example datasetfield names in embodiments may include “dob” to describe date of birth,“ssn” to describe social security number, “phone” to describe a phonenumber, or “hair,” “race,” and “reward.”

In embodiments described herein, multiple APIs or backend applicationsaccessed via a single integration process may operate according todiffering coding languages, dataset structures, dataset field namingconventions or standards. Different coding languages may use differentways of describing routines, data structures, object classes, variables,or remote calls that may be invoked and/or handled during businessintegration processes that involve dataset field values managed by thebackend applications such APIs serve. Thus, a single dataset field valuemay be described in a single integration process using a plurality ofdataset field names, each adhering to the naming conventions set by theAPIs, applications, enterprises, or trading partners through or amongwhich the dataset field value is programmed to integrate.

A user interacting with such an API for a backend application mayidentify such dataset field values based on a description that may ormay not include the actual dataset field name of the dataset fieldvalue. In some circumstances, a dataset field value may be identifiedthrough a search mechanism, or through navigation through a variety ofmenus, for example. The code sets incorporating the actual dataset fieldname for the dataset field value may be automatically generated based onthis user interaction with an API. In other embodiments, the datasetfield value may be identified in a similar way through interaction withthe visual integration process flow user interface described herein. Forexample, the user may create two or more connector visual elements, witheach connector element representing a process taken by a differentapplication (e.g., Salesforce™, or NetSuite™). Because each of suchconnector elements may describe actions taken by a differentapplication, and different applications may adhere to differing codelanguages, each of a plurality of code sets generated based on theseuser-generated connector visual elements may be written in a differentcode language, and may identify dataset field values using differentnaming conventions, or storage structures. Thus, the code instructionsfor retrieving a given dataset field value from a first application maydescribe that dataset field value using a completely different datasetfield name than the code instructions for transmitting the same datasetfield value to a second application. Further, each integration processin embodiments described herein may involve integration of a singledataset field value (e.g., social security number, name, physicaladdress) through several different APIs, for storage (either temporary,or permanent) at any number of address-identified memory locationsthroughout the world, and associated with any number of field names(e.g., ssn, f_name, l_name, address). The code instructions generated inaccordance with the customized data integration process flow modeled viathe user interface in embodiments herein may define the dataset fieldname associated with a given dataset field value at each of suchphysical storage locations.

In embodiments described herein, a runtime engine may be created forexecution of each of these executable customized data integration codeinstructions written based on the user-modeled customized dataintegration process. The runtime engine, and all associated customizeddata integration code instructions or code sets may be transmitted to anend user for execution at the user's computing device, or enterprisesystem, and potentially, behind the user's firewall. Because the userdoes not write the customized data integration code instructionsexecuted by the runtime engine, the user may not know the locations ofservers through which the data to be integrated may pass duringexecution of the runtime engine, or the ways in which dataset fieldvalues may be transformed (e.g., given a different dataset field name)therein. As described above, the dataset field values integrated duringexecution may pass through any number of servers, which may be locatedin various locations around the world. Further, the contents of thesedataset field values may include sensitive personal information (e.g.,personal, secure information, or Personal Identity Information asdefined within the GDPR), which may not be readily apparent based on themetadata associated with the dataset field values, or the dataset fieldnames given to the dataset field values by various APIs or backendapplications involved in the customized data integration process. Amethod is needed to identify, label, and track the ways in which suchsensitive personal information is handled throughout the customized dataintegration process modeled by the user.

Security of personal information has become an increasing concern ofgovernments and regulatory bodies throughout the world during the21^(st) century. As an example, the European Union (EU) has recentlyenacted the General Data Protection Regulation (GDPR), which dictatesrequirements for processing of personal data of EU individuals,regardless of the geographical location of such processing. In short,enterprises doing business within the EU may be required to adhere tothe GDPR, or face stiff fines or penalties. The GDPR contains severalprovisions requiring controllers of sensitive personal information(e.g., enterprises engaged in data integration processes) to applyappropriate technical and organization measures to implement dataprotection principles. Further, upon request of an EU citizen whosepersonal data has been included within an integration process, anadherent to the GDPR (e.g., entity performing data integrationprocesses) must provide adequate explanation of the ways in which suchsensitive personal information has been manipulated or transferred.

One way for an enterprise system executing customized data integrationprocesses to protect against infringement involves tracking the contentof dataset field values being integrated, and the ways in which suchdata is being manipulated. For example, an ability to identify sensitivepersonal information and apply added security measures to customizeddata integration processes involving such sensitive personal informationmay lessen the risk of infringement. In embodiments described herein, ablock chain based data protection system may track theaddress-identified memory locations at which a given dataset labeled ascontaining sensitive personal information has been stored since itscreation or initial access pursuant to customized data integrationprocesses modeled via the web-based user interface described herein.When modeling the customized data integration process via the graphicaluser interface described herein, a user may identify a dataset to becreated, read, updated, or deleted at a first location, and potentiallya second location to which such a dataset, or a dataset field valuewithin such a dataset may be transmitted. In doing so, the user may alsoinitiate block chain tracking of such a dataset, or the dataset fieldvalue, if the dataset is identified as containing potentially sensitivepersonal information, by inserting a block chain visual element into thevisual flow modeling the customized data integration process inembodiments described herein.

The service provider for the graphical user interface through which theuser may model the customized data integration process in embodimentsdescribed herein may generate machine-readable, executable customizeddata integration code instructions for the customized data integrationprocess modeled by the user. The service provider may transmit suchcustomized data integration code instructions as well as a runtimeengine for remote execution of those code instructions at the user'senterprise network. Such customized data integration code instructionsmay include commands to transmit an execution log from the user'senterprise network to the service provider, describing one or moreaspects of datasets for which the user has initiated block chaintracking pursuant to the visual customized data integration process flowmodeled via the graphical user interface. Upon execution of thesecustomized data integration code instructions at the user's enterprisenetwork, and receipt of the execution log at the service provider, theservice provider may create a new metadata tracking block associatedwith these user-identified datasets. Such a metadata tracking block inan embodiment may be associated with one or more dataset field namesdescribing a single dataset field value created, read, updated, ordeleted pursuant to a step within an executed customized dataintegration process. As such, each metadata tracking block may beassociated with a single execution of a customized data integrationprocess, but each execution of a single customized data integrationprocess may be associated with multiple metadata tracking blocks.Further, later executions of the same customized data integrationprocess may also result in creation of new metadata tracking blocksassociated with the same dataset field value. Each of these metadatatracking blocks, generated at multiple steps within the execution of asingle customized data integration process, or generated pursuant tomultiple executions of a customized data integration process, may belinked together to form a block chain describing each of the locationsat which a single dataset field value has been stored. Such block chainsmay be stored at the system provider or a cloud-based storage locationmanaged by the system provider, and may be searched by dataset fieldvalue, or by another metadata search term provided by the user.

A block chain in an embodiment may include a growing list of records inthe form of metadata blocks that are cryptographically linked to oneanother. Each block within a block chain may contain a cryptographichash of the previous block, along with the recorded metadata describeddirectly above. Anyone can add a new block, each block within a blockchain may be publicly available, and multiple copies of each block chainmay exist in multiple locations (e.g., nodes within a decentralizedpeer-to-peer network). In some scenarios, a new block may be added toone version of a given block chain, but not added to another version ofthe same block chain, resulting in two nodes having different version ofthe same block chain. In such a scenario, a single block chain maydevelop a fork, or two different histories of transactions. Each blockchain is equipped with an algorithm for scoring multiple histories inorder to address such inconsistencies. For example, a single node withinthe peer-to-peer network may receive each of the two different versionsof the given block chain described above, and may only keep the versionassociated with the highest score. As the multiple versions circulatethroughout the many nodes of the peer-to-peer network, and nodes discardlower scoring versions, the “correct” or most reliable version of theblock chain is selected over time by majority decision of the nodeswithin the network through which the multiple versions are circulating.

One way in which a fork may appear, resulting in two different versionsof the block chain, occurs when an attempt is made to alter or corruptinformation stored within a previously recorded block, rather thanadding a new block to the block chain. Because each block recorded afterthe corrupted block contains a hash of the corrupted block, the newerblocks will not match the earlier block. Thus, the only way to alterinformation stored in a previously recorded block is to alterinformation stored in every succeeding block as well. However, such analteration of multiple blocks may only alter a single version of themany versions of the same block chain circulating throughout the manynodes of the peer-to-peer network. The chances that a single,significantly altered version of the block chain will receive thehighest score, and thus be designated through majority consensus as themost reliable version, are vanishingly small. Thus, the decentralized,public, cryptographic linking structure of block chains provide asubstantially immutable record of each transaction recorded within eachblock.

The block chains described in embodiments herein may thus store animmutable record for each location at which a single dataset field valuehas been stored over time, even if the dataset field name describingthat dataset field value has changed over time. For example, a singleblock chain in embodiments described herein may be associated with adataset field value “123-45-6789” (e.g., social security number). Such ablock chain may also be associated with two separate dataset field names(e.g., “SSN,” and “social_security_number”) under which the socialsecurity number “123-45-6789” was stored by two separate APIs, pursuantto a single customized data integration process modeled via thegraphical user interface. The block chain based data protection systemin embodiments described herein may track the movement of such a datasetfield value throughout the customized data integration process in such away to assist with the type of reporting required by the GDPR. Asdescribed herein, because multiple steps within the customized dataintegration process may be executed using different coding languages,the code instructions for retrieving a given dataset field value from afirst application/location/enterprise may describe that dataset fieldvalue using a completely different dataset field name than the codeinstructions for storing the same dataset field value at a secondapplication/location/enterprise. Thus, even after a first dataset isidentified at a given step of such a customized data integration processas including a dataset field value containing potentially sensitivepersonal information, a method is needed to also identify other datasetsalso including the same dataset field value as containing potentiallysensitive personal information.

Embodiments of the present disclosure address this issue by creating andreferencing a block chain tracking physical storage locations for eachdataset field value identified as containing potentially sensitivepersonal information, and each dataset field name associated therewithat each recorded physical storage location. Users executing customizeddata integration processes for creation, reading, updating, or deletionof datasets containing such potentially sensitive personal informationmay request a report of known physical storage locations for a givendataset field value over time, pursuant to such executed customized dataintegration processes in embodiments. For example, such reporting mayassist in deterring or lessening potential fines if an infringement ofthe GDPR should occur.

Failure to comply with the GDPR may result in hefty fines. The level offine levied against a non-compliant entity is determined according to avariety of factors, that include the extent of the infringement (e.g.,number of people affected and damage caused thereto), mitigating actstaken by the non-compliant entity following infringement, preventativemeasures taken by the non-compliant entity prior to the infringement,what types of data were impacted by the infringement, and whether thenon-compliant entity promptly notified those who were affected by theinfringement, among others. In the unfortunate event of an infringement,enterprises executing customized data integration processes may at leastdecrease the amount of the resultant penalties by providing detailedmetrics describing data affected by each customized data integrationprocess, individuals whose information was incorporated within suchdata, and the ways in which such data was accessed, copied, transferred,or otherwise manipulated in an infringing customized data integrationprocess. Such detailed information may indicate preventative andmitigating measures were taken, and may assist in notification ofindividuals impacted. Further, providing a tangible number ofindividuals impacted may avoid an assumption of a much higher number ofvictims and damages caused thereto.

A service provider receiving a user reporting instruction requestingreporting for a specifically identified dataset field value inembodiments described herein may access the stored block chainassociated with the user-specified dataset field value. The serviceprovider may then generate a tracking report detailing each of theaddress-identified memory locations at which the user-identified datasetfield value has been stored, and the dataset field name associated withthat dataset field value at each of these address-identified memorylocations. In some embodiments described herein, a user may furthertransmit a user deletion instruction requesting removal of such datasetfield values at one or more of such known physical storage locations.For example, if an employee leaves a position with the user, the usermay wish to remove all potentially sensitive personal informationassociated with that employee at each address-identified memory locationunder the control of the user/employer. The user/employer in someembodiments may identify one or more dataset field values associatedwith the ex-employee within a user deletion instruction transmitted tothe service provider, and the service provider may automaticallyinitiate a deletion process for deletion of each of these identifieddataset field values, at each address-identified memory locationidentified within the block chains associated with each of theseidentified dataset field values. In such a way, the block chain baseddata protection system in embodiments may enable users to comply withGDPR requirements.

FIG. 1 is a block diagram illustrating an information handling system,according to an embodiment of the present disclosure. Informationhandling system 100 can include processing resources for executingmachine-executable code, such as a central processing unit (CPU), aprogrammable logic array (PLA), an embedded device such as aSystem-on-a-Chip (SoC), or other control logic hardware used in aninformation handling system several examples of which are describedherein. Information handling system 100 can also include one or morecomputer-readable media for storing machine-executable code, such assoftware or data. Additional components of information handling system100 can include one or more storage devices that can storemachine-executable code, one or more communications ports forcommunicating with external devices, and various input and output (I/O)devices, such as a keyboard, a mouse, and a video display. Informationhandling system 100 can also include one or more buses operable totransmit information between the various hardware components.

FIG. 1 illustrates an information handling system 100 similar toinformation handling systems according to several aspects of the presentdisclosure. For example, an information handling system 100 may be anymobile or other computing device capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. In a particular embodiment, the information handlingsystem 100 can be implemented using electronic devices that providevoice, video, or data communication. Further, while a single informationhandling system 100 is illustrated, the term “system” shall also betaken to include any collection of systems or sub-systems thatindividually or jointly execute a set, or multiple sets, of instructionsto perform one or more computer functions.

Information handling system 100 can include devices or modules thatembody one or more of the devices or execute instructions for the one ormore systems and modules herein, and operates to perform one or more ofthe methods. The information handling system 100 may execute code 124for the block chain based data protection system 126, or the integrationapplication management system 132 that may operate on servers orsystems, remote data centers, or on-box in individual client informationhandling systems such as a local display device, or a remote displaydevice, according to various embodiments herein. In some embodiments, itis understood any or all portions of code 124 for the block chain baseddata protection system 126 or the integration application managementsystem 132 may operate on a plurality of information handling systems100.

The information handling system 100 may include a processor 102 such asa central processing unit (CPU), a graphics-processing unit (GPU),control logic or some combination of the same. Any of the processingresources may operate to execute code that is either firmware orsoftware code. Moreover, the information handling system 100 can includememory such as main memory 104, static memory 106, drive unit 114, orthe computer readable medium 122 of the block chain based dataprotection system 126, or the integration application management system132 (volatile (e.g. random-access memory, etc.), nonvolatile (read-onlymemory, flash memory etc.) or any combination thereof). Additionalcomponents of the information handling system can include one or morestorage devices such as static memory 106, drive unit 114, and thecomputer readable medium 122 of the block chain based data protectionsystem 126, or the integration application management system 132. Theinformation handling system 100 can also include one or more buses 108operable to transmit communications between the various hardwarecomponents such as any combination of various input and output (I/O)devices. Portions of an information handling system may themselves beconsidered information handling systems.

As shown, the information handling system 100 may further include avideo display 110, such as a liquid crystal display (LCD), an organiclight emitting diode (OLED), a flat panel display, a solid statedisplay, or other display device. Additionally, the information handlingsystem 100 may include a control device 116, such as an alpha numericcontrol device, a keyboard, a mouse, touchpad, fingerprint scanner,retinal scanner, face recognition device, voice recognition device, orgesture or touch screen input.

The information handling system 100 may further include a visual userinterface 112. The visual user interface 112 in an embodiment mayprovide a visual designer environment permitting a user to defineprocess flows between applications/systems, such as between tradingpartner and enterprise systems, and to model a customized businessintegration process. The visual user interface 112 in an embodiment mayprovide a menu of pre-defined user-selectable visual elements and permitthe user to arrange them as appropriate to model a process and may bedisplayed on the video display 110. The elements may include visual,drag-and-drop icons representing specific units of work required as partof the integration process, such as invoking an application-specificconnector, transforming data from one format to another, routing datadown multiple paths of execution by examining the contents of the data,business logic validation of the data being processed, etc.

Further, the graphical user interface 112 allows the user to provideuser input providing information relating to trading partners,activities, enterprise applications, enterprise system attributes,and/or process attributes that are unique to a specific enterpriseend-to-end business integration process. For example, the graphical userinterface 112 may provide drop down or other user-selectable menuoptions for identifying trading partners, application connector andprocess attributes/parameters/settings, etc., and dialog boxespermitting textual entries by the user, such as to describe the formatand layout of a particular dataset to be sent or received, for example,a Purchase Order. The providing of this input by the user results in thesystem's receipt of such user-provided information as an integrationprocess data profile code set.

In some embodiments, the graphical user interface 112 may also allow auser to provide one or more search terms that may be used to identifydataset field values affected by one or more integration processes thatare likely to include sensitive personal information. A user in such anembodiment may interact with such a user interface 112 to include orexclude terms used by the block chain based data protection system 124to track address-identified memory locations at which datasetsidentified by the user as containing potentially sensitive personalinformation may be stored pursuant to one or more customized dataintegration processes. Address-identified memory locations, as referredto herein, include any memory location for storage of data, includinglocations defined by physical, logical, or virtual memory addresses. Inyet another embodiment, a user may employ the graphical user interface112 to search and view information describing such potentially sensitivedataset field values identified in such a manner.

The information handling system 100 can represent a server device whoseresources can be shared by multiple client devices, or it can representan individual client device, such as a desktop personal computer, alaptop computer, a tablet computer, or a mobile phone. In a networkeddeployment, the information handling system 100 may operate in thecapacity of a server or as a client user computer in a server-clientuser network environment, or as a peer computer system in a peer-to-peer(or distributed) network environment.

The information handling system 100 can include a set of instructions124 that can be executed to cause the computer system to perform any oneor more of the methods or computer based functions disclosed herein. Forexample, information handling system 100 includes one or moreapplication programs 124, and Basic Input/Output System and Firmware(BIOS/FW) code 124. BIOS/FW code 124 functions to initialize informationhandling system 100 on power up, to launch an operating system, and tomanage input and output interactions between the operating system andthe other elements of information handling system 100. In a particularembodiment, BIOS/FW code 124 reside in memory 104, and includemachine-executable code that is executed by processor 102 to performvarious functions of information handling system 100. In anotherembodiment (not illustrated), application programs and BIOS/FW codereside in another storage medium of information handling system 100. Forexample, application programs and BIOS/FW code can reside in staticmemory 106, drive 114, in a ROM (not illustrated) associated withinformation handling system 100 or other memory. Other options includeapplication programs and BIOS/FW code sourced from remote locations, forexample via a hypervisor or other system, that may be associated withvarious devices of information handling system 100 partially in memory104, storage system 106, drive unit 114 or in a storage system (notillustrated) associated with network interface device 118 or anycombination thereof. Application programs 124, and BIOS/FW code 124 caneach be implemented as single programs, or as separate programs carryingout the various features as described herein. Application programinterfaces (APIs) such as WinAPIs (e.g. Win32, Win32s, Win64, andWinCE), or an API adhering to a known open source specification mayenable application programs 124 to interact or integrate operations withone another.

In an example of the present disclosure, instructions 124 may executesoftware for tracking and reporting information describing dataset fieldvalues accessed, transferred, copied, or otherwise manipulated during acustomized data integration process, for compliance with governmentalregulations. The computer system 100 may operate as a standalone deviceor may be connected, such as via a network, to other computer systems orperipheral devices.

Main memory 104 may contain computer-readable medium (not shown), suchas RAM in an example embodiment. An example of main memory 104 includesrandom access memory (RAM) such as static RAM (SRAM), dynamic RAM(DRAM), non-volatile RAM (NV-RAM), or the like, read only memory (ROM),another type of memory, or a combination thereof. Static memory 106 maycontain computer-readable medium (not shown), such as NOR or NAND flashmemory in some example embodiments. The disk drive unit 114, theintegration application management system 132, and the block chain baseddata protection system 126 may include a computer-readable medium 122such as a magnetic disk, or a solid-state disk in an example embodiment.The computer-readable medium of the memory, storage devices and theblock chain based data protection system 104, 106, 114, 132 and 126 maystore one or more sets of instructions 124, such as software codecorresponding to the present disclosure.

The disk drive unit 114, static memory 106, and computer readable medium122 of the block chain based data protection system 126, or theintegration application management system 132 may also contain space fordata storage such as an information handling system for managinglocations of executions of customized integration processes in endpointstorage locations. Connector code sets (e.g., customized dataintegration code instructions, deletion code instructions, archive codeinstructions, or notification code instructions), and trading partnercode sets may also be stored in part in the disk drive unit 114, staticmemory 106, or computer readable medium 122 of the block chain baseddata protection system 126, or the integration application managementsystem 132 in an embodiment. In other embodiments, data profile codesets, and runtime engines may also be stored in part or in full in thedisk drive unit 114, static memory 106, or computer readable medium 122of the block chain based data protection system 126, or the integrationapplication management system 132. Further, the instructions 124 of theblock chain based data protection system 126, or the integrationapplication management system 132 may embody one or more of the methodsor logic as described herein.

In a particular embodiment, the instructions, parameters, and profiles124, and the block chain based data protection system 126, or theintegration application management system 132 may reside completely, orat least partially, within the main memory 104, the static memory 106,disk drive 114, and/or within the processor 102 during execution by theinformation handling system 100. Software applications may be stored instatic memory 106, disk drive 114, and the block chain based dataprotection system 126, or the integration application management system132.

Network interface device 118 represents a NIC disposed withininformation handling system 100, on a main circuit board of theinformation handling system, integrated onto another component such asprocessor 102, in another suitable location, or a combination thereof.The network interface device 118 can include another informationhandling system, a data storage system, another network, a gridmanagement system, another suitable resource, or a combination thereof.

The block chain based data protection system 126 and the integrationapplication management system 132 may also contain computer readablemedium 122. While the computer-readable medium 122 is shown to be asingle medium, the term “computer-readable medium” includes a singlemedium or multiple media, such as a centralized or distributed database,and/or associated caches and servers that store one or more sets ofinstructions. The term “computer-readable medium” shall also include anymedium that is capable of storing, encoding, or carrying a set ofinstructions for execution by a processor or that cause a computersystem to perform any one or more of the methods or operations disclosedherein.

In a particular non-limiting, exemplary embodiment, thecomputer-readable medium can include a solid-state memory such as amemory card or other package that houses one or more non-volatileread-only memories. Further, the computer-readable medium can be arandom access memory or other volatile re-writable memory. Additionally,the computer-readable medium can include a magneto-optical or opticalmedium, such as a disk or tapes or other storage device to storeinformation received via carrier wave signals such as a signalcommunicated over a transmission medium. Furthermore, a computerreadable medium can store information received from distributed networkresources such as from a cloud-based environment. A digital fileattachment to an e-mail or other self-contained information archive orset of archives may be considered a distribution medium that isequivalent to a tangible storage medium. Accordingly, the disclosure isconsidered to include any one or more of a computer-readable medium or adistribution medium and other equivalents and successor media, in whichdata or instructions may be stored.

The information handling system 100 may also include the block chainbased data protection system 126, and the integration applicationmanagement system 132. The block chain based data protection system 126,and the integration application management system 132 may be operablyconnected to the bus 108. The block chain based data protection system126 and the integration application management system 132 are discussedin greater detail herein below.

In other embodiments, dedicated hardware implementations such asapplication specific integrated circuits, programmable logic arrays andother hardware devices can be constructed to implement one or more ofthe methods described herein. Applications that may include theapparatus and systems of various embodiments can broadly include avariety of electronic and computer systems. One or more embodimentsdescribed herein may implement functions using two or more specificinterconnected hardware modules or devices with related control and datasignals that can be communicated between and through the modules, or asportions of an application-specific integrated circuit. Accordingly, thepresent system encompasses software, firmware, and hardwareimplementations.

When referred to as a “system”, a “device,” a “module,” or the like, theembodiments described herein can be configured as hardware. For example,a portion of an information handling system device may be hardware suchas, for example, an integrated circuit (such as an Application SpecificIntegrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), astructured ASIC, or a device embedded on a larger chip), a card (such asa Peripheral Component Interface (PCI) card, a PCI-express card, aPersonal Computer Memory Card International Association (PCMCIA) card,or other such expansion card), or a system (such as a motherboard, asystem-on-a-chip (SoC), or a standalone device). The system, device, ormodule can include software, including firmware embedded at a device,such as an Intel® Core class processor, ARM® brand processors, Qualcomm®Snapdragon processors, or other processors and chipset, or other suchdevice, or software capable of operating a relevant environment of theinformation handling system. The system, device or module can alsoinclude a combination of the foregoing examples of hardware or software.In an example embodiment, the block chain based data protection system126, and the integration application management system 132 above and theseveral modules described in the present disclosure may be embodied ashardware, software, firmware or some combination of the same. Note thatan information handling system can include an integrated circuit or aboard-level product having portions thereof that can also be anycombination of hardware and software. Devices, modules, resources, orprograms that are in communication with one another need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices, modules, resources, or programs thatare in communication with one another can communicate directly orindirectly through one or more intermediaries.

In accordance with various embodiments of the present disclosure, themethods described herein may be implemented by software programsexecutable by a computer system. Further, in an exemplary, non-limitedembodiment, implementations can include distributed processing,component/object distributed processing, and parallel processing.Alternatively, virtual computer system processing can be constructed toimplement one or more of the methods or functionality as describedherein.

FIG. 2 is a graphical diagram illustrating a simplified integrationnetwork 200 including a service provider system/server 230 and anenterprise system/network 210 in an embodiment according to the presentdisclosure. Actual integration network topology could be more complex insome other embodiments. As shown in FIG. 2 , an embodiment may includeconventional computing hardware of a type typically found inclient/server computing environments. More specifically, the integrationnetwork 200 in an embodiment may include a conventional user/clientdevice 212, such as a conventional desktop or laptop PC, enabling a userto communicate via the network 220, such as the Internet. In anotheraspect of an embodiment, the user device 212 may include a portablecomputing device, such as a computing tablet, or a smart phone. The userdevice 212 in an embodiment may be configured with conventional webbrowser software, such as Google Chrome®, Firefox®, or MicrosoftCorporation's Internet Explorer® for interacting with websites via thenetwork 220. In an embodiment, the user device 212 may be positionedwithin an enterprise network 210 behind the enterprise network'sfirewall 216, which may be of a conventional type. As a further aspectof an embodiment, the enterprise network 210 may include a businessprocess system 214, which may include conventional computer hardware andcommercially available business process software such as QuickBooks,SalesForce's™ Customer Relationship Management (CRM) Platform, Oracle's™Netsuite Enterprise Resource Planning (ERP) Platform, Infor's™ WarehouseManagement Software (WMS) Application, or many other types of databases.

In an embodiment, the integration network 200 may further includetrading partners 240 and 250 operating conventional hardware andsoftware for receiving and/or transmitting data relating tobusiness-to-business transactions. For example, Walmart® may operatetrading partner system 240 to allow for issuance of purchase orders tosuppliers, such as the enterprise 210, and to receive invoices fromsuppliers, such as the enterprise 210, in electronic data form as partof electronic data exchange processes. Electronic data exchange processin an embodiment may include data exchange via the world wide web. Inother embodiments, electronic data exchange processes may include dataexchange via FTP or SFTP.

In an embodiment, a provider of a service (“service provider”) forcreating on-demand, real-time creation of customized data integrationsoftware applications may operate a service provider server/system 230within the integration network 200. The service provider system/server230 may be specially configured in an embodiment, and may be capable ofcommunicating with devices in the enterprise network 210. The serviceprovider system/server 230 in an embodiment may host a customized dataintegration process-modeling user interface in an embodiment. Such acustomized data integration process-modeling user interface may allow auser or the block chain based data protection system to model acustomized data integration process including one or more sub-processesfor data integration through a business process data exchange between anenterprise system/network 210 and outside entities or between multipleapplications operating at the business process system 214. Thecustomized data integration process modeled in the integrationprocess-modeling user interface in an embodiment may be a singlebusiness process data exchange shown in FIG. 2 , or may include severalbusiness process data exchanges shown in FIG. 2 . For example, theenterprise system/network 210 may be involved in a business process dataexchange via network 220 with a trading partner 1, and/or a tradingpartner 2. In other example embodiments, the enterprise system/network210 may be involved in a business process data exchange via network 220with a service provider located in the cloud 232, and/or an enterprisecloud location 218. For example, one or more applications between whicha dataset field value may be transferred, according to embodimentsdescribed herein, may be located remotely from the enterprise system210, at a service provider cloud location 232, or an enterprise cloudlocation 218.

The block chain based data protection system, or a user of anintegration process-modeling user interface in an embodiment may modelone or more business process data exchanges via network 220 within acustomized data integration process by adding one or more visualconnector integration elements or code sets to an customized dataintegration process flow. These visual connector integration elements inan embodiment may model the ways in which a user wishes data to beaccessed, moved, and/or manipulated during the one or more businessprocess data exchanges. Each visual connector element the user adds tothe customized data integration process flow diagram in an embodimentmay be associated with a pre-defined subset of customized dataintegration code instructions stored at the service providersystems/server 230 in an embodiment. Upon the user modeling thecustomized data integration process, the service provide system/server230 in an embodiment may generate a runtime engine capable of executingthe pre-defined subsets of customized data integration code instructionsrepresented by the visual connector integration elements chosen by theuser. The runtime engine may then execute the subsets of customized dataintegration code instructions in the order defined by the modeled flowof the visual connector integration elements given in the customizeddata integration process flow diagram. In such a way, a customized dataintegration process may be executed without the user having to access,read, or write the code instructions of such a customized dataintegration process.

In other aspects of an embodiment, a user may initiate a businessprocess data exchange between one cloud service provider 232 and onecloud enterprise 218, between multiple cloud service providers 232 withwhich the enterprise system 210 has an account, or between multiplecloud enterprise accounts 218. For example, enterprise system 210 mayhave an account with multiple cloud-based service providers 232,including a cloud-based SalesForce™ CRM account and a cloud-basedOracle™ Netsuite account. In such an embodiment, the enterprise system210 may initiate business process data exchanges between itself, theSalesForce™ CRM service provider and the Oracle™ Netsuite serviceprovider.

In some embodiments, a single customized data integration process mayinvolve movement of dataset field values among several differententities, in series. For example, a dataset field value may travel vianetwork 220 from the enterprise system 210, to enterprise cloud 218,then cloud service provider 232, and ultimately to trading partner 240.A dataset field value may move, undergoing temporary or permanentstorage or other manipulations, through potentially hundreds of suchdifferent address-identified memory locations, at potentially hundredsof geographic locations within a single customized data integrationprocess in some embodiments.

FIG. 3A is a graphical diagram illustrating a user-generated flowdiagram of a customized data integration process for exchange ofelectronic data records according to an embodiment of the presentdisclosure. The flow diagram in an embodiment may be displayed within aportion of a graphical user interface that allows the user to build theprocess flow, deploy the customized data integration process modeledthereby (e.g., by selecting the deploy tab 364), manage dataset fieldvalues manipulated by such a customized data integration process (e.g.,by selecting the manage tab 366), and to view high-level metricsassociated with execution of such a customized data integration process(e.g., by selecting the dashboard tab 360). The user may build theprocess flow and view previously built process flow diagrams byselecting the “Build” tab 362 in an embodiment. A user may generate aflow diagram in an embodiment by providing a chronology ofprocess-representing integration elements via the use of an integrationprocess-modeling user interface. In some embodiments, the integrationprocess-modeling user interface may take the form of a visual userinterface. In such embodiments, the user-selectable elementsrepresenting integration sub-processes (e.g. connector integrationelements) may be visual icons.

An integration process-modeling user interface in an embodiment mayprovide a design environment permitting a user to define process flowsbetween applications/systems, such as between trading partner andenterprise systems, between on-site data centers and cloud-based storagemodules, or between multiple applications, and to model a customizeddata integration process. Such an integration process-modeling userinterface in an embodiment may provide a menu of pre-defineduser-selectable elements representing integration sub-processes andpermit the user or the block chain based data protection system toarrange them as appropriate to model a full, customized data integrationprocess. For example, in an embodiment in which the integrationprocess-modeling user interface is a visual user interface, the elementsmay include visual, drag-and-drop icons representing specific units ofwork (known as process components) required as part of the customizeddata integration process. Such process components in an embodiment mayinclude invoking an application-specific connector to access, and/ormanipulate data. In other embodiments, process components may includetasks relating to transforming data from one format to another, routingdata down multiple paths of execution by examining the contents of thedata, business logic validation of the data being processed, etc.

Each process component as represented by integration sub-process iconsor elements may be identifiable by a process component type, and mayfurther include an action to be taken. For example, a process componentmay be identified as a “connector” component. Each “connector”component, when chosen and added to the process flow in the integrationprocess-modeling user interface, may allow the block chain based dataprotection system or a user to choose from different actions the“connector” component may be capable of taking on the data as it entersthat process step. Further the integration-process modeling userinterface in an embodiment may allow the user to choose the dataset uponwhich the action will be taken. The action and dataset the user choosesmay be associated with a connector code set, via the integrationapplication management system, which may be pre-defined and stored at asystem provider's memory in an embodiment. The integration applicationmanagement system operating at least partially at a system providerserver/system in an embodiment may generate a dynamic runtime engine forexecuting these pre-defined subsets of code instructions correlated toeach individual process-representing visual element (process component)in a given flow diagram in the order in which they are modeled in thegiven flow diagram, or by the block chain based data protection systemin a non-visual format.

In an embodiment, a user may choose a process component it uses oftenwhen interfacing with a specific trade partner or application, anddefine the parameters of that process component by providing parametervalues specific to that trading partner or application. If the userwishes to use this process component, tailored for use with thatspecific trading partner or application repeatedly, the user may savethat tailored process component as a trading partner or component namedspecifically for that application. For example, if the user oftenaccesses NetSuite™ or SalesForce™, the user may create a databaseconnector process component, associated with a pre-built connector codeset that may be used with any database, then tailor the databaseconnector process component to specifically access NetSuite™ orSalesForce™ by adding process component parameters associated with oneof these applications. If the user uses this process component inseveral different integration processes, the user may wish to save thisprocess component for later use by saving it as a NetSuite™ orSalesForce™ process component. In the future, if the user wishes to usethis component, the user may simply select the NetSuite™ or SalesForce™component, rather than repeating the process of tailoring a genericdatabase connector process component with the specific parametersdefined above.

As shown in FIG. 3A, such process-representing visual elements mayinclude a start element 302, a message element 304, a map element 306, ablock chain tracking element 308, a connector element 310, and a stopelement 312. Other embodiments may also include a branch element, adecision element, a data process element, or a process call element, forexample. A connector element 310, and a start element 302 in anembodiment may represent a sub-process of a customized data integrationprocess describing the accessing and/or manipulation of data. The startelement 302 in an embodiment may also operate as a connector element.

In an embodiment, a start element 302 may operate to begin a customizeddata integration process flow, and a stop element 312 may operate to enda customized data integration process flow. As discussed above, eachvisual element may require user input in order for a particularenterprise or trading partner to use the resulting process. The startelement 302 in an embodiment may further allow or require the user toprovide data attributes unique to the user's customized data integrationprocess, such as, for example, the source of incoming data to beintegrated. For example, the user may use a connector element to definea connection (e.g., an application managing a dataset upon which actionis to be taken), and the action to be taken. A user may use a connectorelement to further define a location of such a dataset, according to thelanguage and storage structure understood by the application managingsuch a dataset. In addition, the dataset to be accessed according tosuch a start element 302 may be identified by a dataset field name givenin a format that adheres to the code language and storage structure usedby the application/location/enterprise at which such a dataset may beaccessed.

A map element 306, or TransformMap element in an embodiment mayassociate a first dataset field name for a dataset field value beingretrieved from a first application or source with a second dataset fieldname under which that dataset field value will be stored at a secondapplication or destination. A user may also provide an operation namethat describes the purpose for changing the dataset field names of thedataset field value in such a way. Because a single customized dataintegration process may transmit dataset field values between or amongseveral sources and destinations, a process flow may include several ofthese mapping elements 306, sometimes placed in series with one another.This may result in a single dataset field value receiving severaldifferent dataset field names as it moves from various sources tovarious destinations throughout the customized data integration process.

The customized data integration code sets associated with the visualelements 302, 304, 306, 308, 310, and 312, including those associatedwith the connection location and action to be taken within a connectorelement may be written in any programming code language so long as theyare consistent with one another. Thus, the process-representing elementsin an embodiment may be programming language-agnostic. Using suchprocess-representing elements in an embodiment, a user may model anend-to-end customized data integration process between multipleapplications that each use different naming conventions and storagestructures for storage of dataset field values. As a result, a singledataset field value accessed at the start element 302 and transmitted toa second location at the connector element 310 in an embodiment may beidentified at the start element 302 with a completely different datasetfield name (e.g., “Social_Security_Number”) than the dataset field name(e.g., “SSN”) used to identify the exact same dataset field value at theconnector element 310.

If a user anticipates a modeled customized data integration process mayaccess, copy, transmit, or otherwise manipulate a dataset field valuelikely to include sensitive personal information (e.g., personalinformation protected under the GDPR), the user may provide a user blockchain instruction by inserting a block chain tracking visual element 308identifying such dataset field values within the modeled customized dataintegration process flow. Such a user block chain instruction may resultin the generation of a block containing metadata describing theaddress-identified memory location at which the dataset field valuelikely to include sensitive personal information is stored, pursuant tothe integration process modeled within the process flow of FIG. 3B. Ifthe integration process modeled in FIG. 3B results in this dataset fieldvalue being stored at multiple locations, multiple blocks may becreated, with each block describing one of the multiple locations atwhich the dataset field value has been stored. Similarly, if theintegration process modeled in FIG. 3B is executed multiple times,multiple blocks may be created, with each block describing one of thetimes at which the integration process was executed to store the datasetfield value at the same or different locations. Each of these multipleblocks in an embodiment may be cryptographically linked to one anotherto form a block chain, which may be stored at one of a plurality ofnodes (e.g., separate physical, logical, or virtual locations withinmemory for one or more servers or information handling systems within apeer-to-peer network).

As described herein, each block within such a block chain may contain acryptographic hash of the previous block, along with the recordedmetadata described directly above. Anyone can add a new block, eachblock within a block chain may be publicly available in some examples orotherwise available within a particular enterprise, and multiple copiesof each block chain may exist in multiple locations (e.g., nodes withina decentralized peer-to-peer network). In some scenarios, a new blockmay be added to one version of a given block chain, but not added toanother version of the same block chain, resulting in two nodes havingdifferent version of the same block chain. In such a scenario, a singleblock chain may develop a fork, or two different histories oftransactions. Each block chain is equipped with an algorithm for scoringmultiple histories in order to address such inconsistencies. Forexample, a single node within the peer-to-peer network may receive eachof the two different versions of the given block chain described above,and may only keep the version associated with the highest score. As themultiple versions circulate throughout the many nodes of thepeer-to-peer network, and nodes discard lower scoring versions, the“correct” or most reliable version of the block chain is selected overtime by majority decision of the nodes within the network through whichthe multiple versions are circulating.

One way in which a fork may appear, resulting in two different versionsof the block chain, occurs when an attempt is made to alter or corruptinformation stored within a previously recorded block, rather thanadding a new block to the block chain. Because each block recorded afterthe corrupted block contains a hash of the corrupted block, the newerblocks will not match the earlier block. Thus, the only way to alterinformation stored in a previously recorded block is to alterinformation stored in every succeeding block as well. However, such analteration of multiple blocks may only alter a single version of themany versions of the same block chain circulating throughout the manynodes of the peer-to-peer network. The chances that a single,significantly altered version of the block chain will receive thehighest score, and thus be designated through majority consensus as themost reliable version, are vanishingly small. Thus, the decentralized,cryptographic linking structure of block chains provide a substantiallyimmutable record of each transaction recorded within each block. Inembodiments herein, the block chain system may be utilized to provide asubstantially immutable record of status and activity relating topotentially sensitive personal information as handled or managed by anautomated integration process.

Returning to FIG. 3A, a user may identify a dataset field value that shewishes to track using block chain technology in an embodiment, bydirectly identifying the dataset field value, or through a search forspecific terms within metadata associated with datasets. Upon insertionof the block chain tracking visual element 308 into the integration flowshown in FIG. 3A in an embodiment, a user may be prompted to providesuch user-specified search terms to be used to identify datasets beingintegrated by the modeled customized data integration process that maycontain potentially sensitive personal information or to identify suchdatasets by a specific dataset field value. The user may further defineone or more search terms that may be used to locate the metadatatracking block chain for that dataset in the future, via the graphicalvisual user interface. For example, the user may identify a datasetfield value “xxx-xx-xxxx” (e.g., representing a social security number)via the block chain tracking visual element 308 by directly enteringthis value, then provide search terms such as “social_security_number,”or “SSN” that may be used in the future to locate the block chain fortracking a specific dataset field value or any dataset field valuefalling under the search term (i.e., a specific social security numberor all social security numbers depending on the search context). In someembodiments, Boolean search operations may be supported, such that theuser may locate block chains associated with multiple search terms. Inthese embodiments, the user may associate the dataset field value for aspecific social security number “123-45-6789” with a search term“social_security_number” that identifies the dataset field nameassociated with the dataset field value within the dataset, as well asthe search terms “John Doe” and “employee_name” identifying the a fieldvalue “John Doe” for the field name “employee_name” associated with thissocial security number in another dataset. In such a way, the user mayuse the graphical visual user interface to define a dataset field valueto be tracked using block chain, as well as multiple search terms forlocating such a block chain after the integration process has beenexecuted. By defining the dataset field value or by providinguser-specified search terms in such a way, the user may be said to haveidentified one or more datasets containing sensitive personalinformation.

In other example embodiments, a user may provide such user-specifiedsearch terms to be used to identify datasets containing potentiallysensitive personal information, such as medical data. For example, theuser may identify a dataset field value associated with a dataset fieldname “BP” or “blood_pressure,” via the block chain tracking visualelement 308 by directly entering this value, then provide search termssuch as “BP,” or “blood pressure” that may be used in the future tolocate the block chain for tracking this dataset field value. As anotherexample, the user may identify a dataset field value associated with adataset field name “height,” by directly entering this value, thenprovide search terms such as “height” that may be used in the future tolocate the block chain for tracking this dataset field value. As yetanother example, the user may identify a dataset field value associatedwith a dataset field name “weight,” by directly entering this value,then provide search terms such as “weight” that may be used in thefuture to locate the block chain for tracking this dataset field value.

The block chain tracking visual element 308 in such an embodiment may beassociated with code instructions directing creation of an execution logthat includes metadata associated with such identified datasets,including the address-identified memory locations at which the datasetis stored pursuant to the modeled customized data integration processduring later executions thereof, as well as the dataset field namesunder which such identified dataset field values are stored at thoseaddress-identified memory locations. Such code instructions may furtherinclude a command to transmit the generated execution log with suchmetadata from the remote location at which the customized dataintegration process is later executed to the service provider managingthe customized data integration process-modeling user interface shown inFIG. 3A.

FIG. 3B is a graphical diagram illustrating a user-generated flowdiagram of a deletion process providing automatic deletion of electronicdata records containing personal information from one or more storagelocations according to an embodiment of the present disclosure. Asdescribed herein, a user may request removal dataset field valuesidentified as potentially containing sensitive personal information atone or more known storage locations. For example, if an employee leavesa position with the user, the user may wish to remove all potentiallysensitive personal information associated with that employee at eachaddress-identified memory location under the control of theuser/employer. The user/employer in some embodiments may identify one ormore dataset field values associated with the ex-employee to the serviceprovider. The service provider in such an embodiment may automaticallycreate a new process flow for deletion of the user-identified datasetfield values at each location identified within the block chainsassociated with each identified dataset field value. In such a way, theblock chain based data protection system in embodiments may enable usersto comply with GDPR requirements or to remove all sensitive personalinformation relating to specific individuals, such as when thatindividual no longer participates in the enterprise system storing suchinformation. In other embodiments, the block chain based data protectionsystem in embodiments may enable users to comply with GDPR requirementsor to remove all sensitive personal information that may have beenmanipulated or utilized within an integration process but must beremoved or tracked relating to any individuals or a subset ofindividuals, such as when one or more database locations orentity-controlled locations are no longer participating or entitled tomaintain such information in relation to the enterprise system operatinga business integration that stores such information at such a databaselocation.

Upon identification of dataset field values potentially containingsensitive personal information in an embodiment, the block chain baseddata protection system may generate a data deletion process flow thatmodels deletion of data identified within block chains generatedpursuant to the customized data integration process modeled in FIG. 3A.For example, the data deletion process flow modeled in FIG. 3B may begenerated automatically by the block chain based data protection systemupon user input identifying one or more dataset field values that shouldbe deleted. As shown in FIG. 3B, such a data deletion process flow mayinclude a start element 314, a block chain tracking element 316, aconnector element 318, a validation/authorization sub-process element320, an archive sub-process element 322, a notification element 324, areturn data element 326, and a stop element 328.

As discussed above, the start element 314 in an embodiment may allow orrequire the user or the block chain based data protection system toprovide data attributes unique to the user's specific customized dataintegration process, such as, for example, the source of data to bedeleted. As also described herein, the user may identify one or moredatasets for deletion by providing a user-specified search term. Theblock chain based data protection system in such an embodiment mayreceive this user-specified search term and search the block chainsgenerated pursuant to the block chain tracker visual element 308depicted in FIG. 3A for matching blocks. For example, a user may providea user-specified search term “social,” which may match a blockdescribing storage at a first location (e.g., Netsuite™) of a datasetfield name “social_security_number,” having a dataset field value“123-45-6789.” In other embodiments, the user may provide a datasetfield value for removal rather than a search term. In such embodiments,the block chain based data protection system may retrieve several blockswithin a block chain, all of which may be associated with theuser-specified dataset field value.

In other example embodiments, a user may provide such a user-specifiedsearch term “blood pressure,” which may match a block describing storageat a first location of a dataset value having a dataset field name fieldname “BP,” or “blood pressure.” As another example, a user may providesuch a user-specified search term “height,” which may match a blockdescribing storage at a first location of a dataset value having adataset field name field name “height.” As yet another example, a usermay provide such a user-specified search term “weight,” which may matcha block describing storage at a first location of a dataset value havinga dataset field name field name “weight.”

The block chain based data protection system in an embodiment mayretrieve or access all blocks in the same chain with this blockdescribing storage of a dataset field name “social_security_number.” Forexample, the block chain may further include another block describingstorage at a second location (e.g., SalesForce™) of a dataset field name“SSN,” having the same dataset field value “123-45-6789.” Upon receivinga user deletion instruction, the block chain based data protectionsystem in such an embodiment may identify both the datasets within thisblock chain (e.g., having the dataset field name “SSN,” and having thedataset field name “social_security_number”) for removal from the firstand second locations, respectively. These dataset field names (e.g.,“SSN,” and “social_security_number”) and the first and second locationsof those datasets may be provided within data attributes of the startelement 314 in an embodiment. In some embodiments, the start element 314may identify more than one dataset for deletion at more than onelocation. In other embodiments, the start element 314 may identify asingle dataset (e.g., identified at only one of the blocks within theblock chain) for deletion. In such an embodiment, the block chain baseddata protection system may generate a separate data deletion processflow model for each block within the block chain (e.g., one datadeletion process flow for deletion of each dataset described in eachindividual block of the block chain).

The block chain based data protection system in an embodiment may alsoinsert a block chain tracking visual element 316 identifying the datasetto be deleted. The block chain based data protection system may furtherdefine one or more search terms that may be used to locate the metadatatracking block chain generated pursuant to visual element 316 for thatdataset in the future, via the graphical visual user interface. Forexample, the block chain based data protection system may identify adataset field value (e.g., “123-45-6789”) based on the received userinput identifying the dataset to be deleted, then provide search termssuch as “deleted,” or “removed” that may be used in the future to locatethe block chain for tracking deletion of this dataset field value.

The deletion process flow modeled in FIG. 3B may also include aconnector element 318, defining an action to be taken on the datasetidentified by the user to be deleted. For example, the block chain dataprotection system in an embodiment may automatically set the connectorelement 318 to delete the dataset (e.g., dataset field name and datasetfield value) from the location at which the dataset is stored andaccessed at start element 314. Some such deletion methods may requireauthorization or validation that the user possesses necessarilycredentials to perform such a deletion. Thus, the data deletion processflow may include a validation/authorization sub-process element 320which may operate to provide such authorization or validation ofcredentials. In some embodiments, the block chain data protection systemmay prompt the user to provide such credentials or authorization viaanother graphical user interface, prior to execution of the datadeletion process flow modeled in FIG. 3B. In other embodiments, the usermay provide such authorization or credentials simultaneously withidentifying the datasets to be deleted or removed. In either of theseembodiments, the block chain based data protection system may includesuch user-provided authorization or credentials when automaticallygenerating the validation/authorization sub-process element 320 (e.g.,as data profiles associated with the validation/authorizationsub-process element 320).

The deletion process flow depicted in FIG. 3B may also include anarchive sub-process element 322 operating to store a copy of the deleteddataset in a secured archive. Such an archiving of deleted datasets maybe provided in case of a rollback in which the user wishes to restorethe deleted dataset back to its original location, defined within thestart element 314. In such an embodiment, the archive sub-processelement 322 may further associate the archived dataset within thearchive storage location with this original storage location from whichthe dataset is being deleted.

A notification visual element 324 may also be included within thedeletion process flow depicted in FIG. 3B. Such a notification visualelement 324 in an embodiment may operate to transmit a notification tothe enterprise network executing the deletion process that the deletionprocess has been completed. The notification transmitted may furtheridentify each dataset deleted, as well as metadata associated with eachdataset (e.g., location from which dataset was deleted, date and time ofdeletion, identification of process executed to perform such adeletion). The data deletion process flow thus modeled may also includea return data visual element 326 operating to transmit a success reportor a failure report to the enterprise network indicating whether thedeletion of datasets automatically set for deletion by the block chainbased data protection system has been successfully completed uponexecution of the data deletion process. The data deletion process mayend with a stop element 328, indicating completion of the process flow.In such a way, the block chain based data protection system in anembodiment may automatically generate a deletion process operating toautomatically delete one or more datasets identified through user input.

FIG. 4 is a block diagram illustrating a block chain module storingmetadata tracking block chains associated with dataset field valuesidentified by the user as potentially containing sensitive personalinformation according to an embodiment of the present disclosure. Asdescribed herein, an ability to identify sensitive personal informationand apply added security measures to data integration processesinvolving such sensitive personal information may lessen the risk ofinfringement of the GDPR and increase security of private information.As also described herein, a user in an embodiment may identify a datasetas containing sensitive personal information by inserting a block chaintracking visual element identifying that dataset into the customizeddata integration process flow modeled by the user (e.g., as describedwith reference to FIG. 3A above). A new block within a block chain,storing metadata for describing each action taken on a dataset fieldvalue within such an identified dataset may be generated and stored bythe service provider for each execution of the customized dataintegration process involving that dataset in an embodiment.

For example, a user may access the graphical visual user interfacedescribed with reference to FIG. 3A from the enterprise system/network410 in an embodiment. The user may create and edit customized dataintegration process flows via the graphical visual user interface, thustransmitting user instructions 402 that model the user's integrationprocess flow to a data integration processing module 431 of theintegration application management system 432 maintained and operated bythe service provider system/server managing the graphical visual userinterface. Such user instructions in an embodiment may include aninstruction to insert any of the visual elements described withreference to FIG. 3A into the customized data integration process flowmodeled by the user, which may specifically include a user block chainreporting instruction identifying a dataset field value for which atracking block chain may be generated. A user in an embodiment mayidentify such a dataset field value by providing the exact dataset fieldvalue (e.g., “123-45-6789”) within the user block chain instruction. Theuser may also provide, within the user block chain instruction, one ormore user-specified search terms (e.g., “social_security_number”) thatmay be found within the dataset field name associated with the datasetfield value, which may be used to search for the user-specified datasetfield value (e.g., “123-45-6789”) following execution of the customizeddata integration process. Thus, the instructions 402 in an embodimentmay also include such an identification of a dataset field value, oruser-specified search terms that may be used to identify a dataset fieldvalue in the future.

The service provider system/server in an embodiment may also manage ablock chain based data protection system 426, including a master datamanagement module 433 and a block chain module 434. The block chainmodule 434 in an embodiment may operate to store and log blocks withinblock chains in an embodiment. The master data management module 433 inan embodiment may operate to manage storage by, and retrieval of blockchains from the block chain module 434, according to received userinstructions. In some embodiments, the master data management module mayalso compile information retrieved from block chains into user-requestedreports, or manage deletion of user-specified datasets identified inretrieved blocks or block chains. Instructions 402 may define each stepof a user-defined data integration process, including user block chaininstructions to track storage locations for a user-specified datasetthat may contain sensitive personal information. These user block chaininstructions may be supplied by the user in an embodiment by inserting ablock chain visual element into the customized data integration processflow and providing a user-specified dataset field value. As describedwith reference to FIG. 3A, the user may define one or moreuser-specified search terms that may be used to locate the metadatatracking block chain for a given dataset field value in the future(e.g., following execution of the customized data integration processmodeled in FIG. 3A), via the graphical visual user interface. Forexample, the user instructions 402 may identify a dataset field value“123-45-6789,” as well as search terms such as “social_security_number,”“SSN,” or “John Doe” that may be used in the future to locate the blockchain for tracking this dataset field value.

In other example, the user may identify a dataset field value associatedwith a dataset field name “BP” or “blood_pressure,” via the block chaintracking visual element 308 by directly entering this value, thenprovide search terms such as “BP,” or “blood pressure” that may be usedin the future to locate the block chain for tracking this dataset fieldvalue. As another example, the user may identify a dataset field valueassociated with a dataset field name “height,” by directly entering thisvalue, then provide search terms such as “height” that may be used inthe future to locate the block chain for tracking this dataset fieldvalue. As yet another example, the user may identify a dataset fieldvalue associated with a dataset field name “weight,” by directlyentering this value, then provide search terms such as “weight” that maybe used in the future to locate the block chain for tracking thisdataset field value.

The data integration processing module 431 of the integrationapplication management system 432 in an embodiment may operate within astandalone information handling system, within a single server, across aplurality of servers or information handling systems, or within a cloudinfrastructure. In an embodiment, the data integration processing module431 may operate to generate or customize code instructions (e.g.,connector code sets) executable by the enterprise system network 410 toperform the data integration process modeled by the user via thegraphical user interface. The data integration processing module 431 inan embodiment may transmit machine-executable code instructions and aruntime engine 406 for later execution of the modeled customized dataintegration process to the enterprise system/network 410. Such codeinstructions 406 may include commands to transmit an execution log fromthe user's enterprise network 410 to the integration applicationmanagement system 432 or the block chain based data protection system426 of the service provider describing one or more aspects of datasetsfor which the user has initiated block chain tracking pursuant to thevisual integration flow modeled via the graphical user interface.

In other aspects, the data integration processing module 431 may receivethe user identification 402 of a dataset field value (e.g.,“123-45-6789”) to be tracked, and may transmit instructions 404 tocreate or update a block chain for such tracking to the block chainmodule 434. These instructions 404 may identify the dataset field value(e.g., “123-45-6789”), as well as the customized data integrationprocess in which such a dataset will be created, read, updated, ordeleted pursuant to the user instructions 402. The block chain module434 in an embodiment may create a new metadata tracking block for thedataset field value identified by the user for tracking, which may beupdated following execution of the customized data integration processcode instructions 406 transmitted to the enterprise system 410, toinclude locations at which that dataset field value has been stored orotherwise manipulated pursuant to that customized data integrationprocess (e.g., the customized data integration process modeled in anembodiment described with reference to FIG. 3A). The newly created blockin such an embodiment may be stored in the block chain module 434 of theblock chain based data protection system 426 at the service provider,and may be accessed and managed by the master data management module433. The block chain hyper ledger 435 in such an embodiment may store anassociation between the metadata tracking block and the user-specifieddataset field value and the one or more user-specified search terms orkeys supplied by the user (e.g., “social_security_number,” “SSN,” or“John Doe”) that may be used to later identify the block chain for theidentified dataset field value (e.g., “123-45-6789”). In someembodiments, the block chain module 434 may further compare the newlycreated metadata tracking block against other node registers operatingwithin the service provider, the enterprise system 410, or external toboth of these, in order to ensure the accuracy of information storedwithin the newly created metadata tracking block.

FIG. 5 is a block diagram illustrating a master data management modulefor tracking storage and manipulation of a user-specified dataset fieldvalue potentially containing sensitive personal information, throughexecution of a user-modeled customized data integration processaccording to an embodiment of the present disclosure. Upon receipt ofthe runtime engine and code instructions for execution of theuser-modeled customized data integration process at the enterprisesystem 510 in an embodiment (as described above with reference to FIG. 4), the user may initiate the runtime engine to execute those codeinstructions.

Pursuant to such an execution, an information handling system within theenterprise system 510 may establish communication with one or moreremote server locations or backend applications managing the data to beintegrated. For example, the enterprise system 510 may establishcommunication with a trading partner, or with a cloud-based storagelocation or application as discussed with respect to FIG. 2 above. Suchtrading partners or applications may manage data at a database 542, adata lake 544, or within one or more files 546 stored on a server in anembodiment. The enterprise system 510 in such an embodiment mayestablish such a connection via a network, for example.

The enterprise system 510 in an embodiment may execute code instructionsincluding the creation, reading, updating, or deletion (CRUD) of one ormore datasets pursuant to the customized data integration processmodeled by the user via the graphical user interface described above,for example in an embodiment described with respect to FIG. 3A. A singlecustomized data integration process, modeled in a single customized dataintegration process flow, may include one or more of these actions(e.g., CRUD) performed upon a plurality of different datasets, incommunication with one or more remote locations (e.g., database 542,data lake 544, or files 546). For example, the enterprise system 510 inan embodiment may execute code instructions 501 of a customized dataintegration process to read a dataset including the dataset field name“social” and the dataset field value “123-45-6789” from the database542. The enterprise system 510 in such an embodiment may also executecode instructions 502, pursuant to the same or another customized dataintegration process, to update a dataset having a dataset field name“SSN” stored at the data lake 544 to include a dataset field value of“123-45-6789.” Similarly, the enterprise system 510 in such anembodiment may also execute code instructions 503, pursuant to the sameor another customized data integration process, to create a datasethaving a dataset field name “social_security_number” stored in files 546to include a dataset field value of “123-45-6789.” As described herein,the naming conventions or dataset field names applied to certain datasetfield values may vary among applications. For example, the database 542in an embodiment may be managed within a Customer RelationshipManagement (CRM) platform, such as SalesForce™, while the data lake 544is managed by an Enterprise Resource Planning (ERP) platform, such asOracle NetSuite™. While both the CRM and ERP in such an exampleembodiment may store datasets including the same social security number(e.g., “123-45-6789”), those datasets may have different dataset fieldnames (e.g., “social,” or “SSN”), depending on the conventions appliedby each platform. Thus, a single customized data integration process mayinclude accessing, storing, or updating the same dataset field value(e.g., social security number “123-45-6789”) at multiple locations, witheach location associating the dataset field value with a differentdataset field name (e.g., “social,” “SSN,” or “social_security_number”).

Following execution of code instructions 501, 502, and 503, includingcreation, reading, and updating of a single dataset field value atmultiple locations (e.g., 542, 544, and 546) as executed by the runtimeengine at the enterprise system 510, the enterprise system 510 in anembodiment may generate an execution log describing such an execution.The execution log in such an embodiment may include metadata for thedatasets created, read, updated, or deleted pursuant to the codeinstructions 501, 502, and 503. Such metadata may describe the datasetfield name and dataset field values for each dataset involved, whethereach dataset was created, read, updated, or deleted, during thecustomized data integration process(es), and the address-identifiedmemory locations involved in such an action. For example, an executionlog in an embodiment may include a first entry indicating a firstdataset with a dataset field name “social” and a dataset field value“123-45-6789” was read from database 542, a second entry indicating asecond dataset with a dataset field name “SSN” was updated to includedataset field value “123-45-6789” at data lake 544, and a third entryindicating a third dataset with a dataset field name“social_security_number,” and a dataset field value “123-45-6789” wascreated within files 546. In other embodiments, in which instructions501, 502, and 503 are executed pursuant to separate customized dataintegration processes, or separate executions of the same customizeddata integration processes, the first, second, and third entriesdescribed directly above may appear, respectively, in three separateexecution logs.

The execution log in such an embodiment may also identify the enterprisesystem 510, the time of execution, if any of the datasets created, read,updated, or deleted have been flagged by the user for block chaintracking, and the customized data integration process that was executed.Identification of the customized data integration process may besufficient to further identify the customized data integration processflow created by the user via the graphical visual user interface, (e.g.,the customized data integration process flow described above in anembodiment with reference to FIG. 3A). Code instructions for thecustomized data integration process in an embodiment may direct creationof the execution log, and may include instructions to associate anydataset field values identified within a user block chain instructionwith a flag for block chain tracking. For example, the code instructionsfor the customized data integration process in an embodiment may includecode instructions to generate an execution log that applies a blockchain tracking flag to a first entry describing a first dataset with adataset field name “social” and a dataset field value “123-45-6789,” toa second entry describing the second dataset with a dataset field name“SSN” and a dataset field value “123-45-6789,” and to a third entrydescribing the third dataset with a dataset field name“social_security_number.”

The enterprise system 510 in such an embodiment may transmit theexecution log 504 to the master data management module 533 of the blockchain based data protection system 526 managed by the service provider.In other embodiments, in which instructions 501, 502, and 503 areexecuted pursuant to separate customized data integration processes, orseparate executions of the same customized data integration processes,resulting in three separate execution logs, the enterprise system 510may transmit each of these three separate execution logs to the masterdata management module 533 of the block chain based data protectionsystem 526. The master data management module 533 of the block chainbased data protection system 526 in an embodiment may operate within astandalone information handling system, within a single server, across aplurality of servers or information handling systems, or within a cloudinfrastructure.

Upon receipt of the execution log at the block chain based dataprotection system 526 of the service provider, the master datamanagement module 533 may determine whether the execution log includesmetadata for any datasets flagged by the user for block chain tracking.If the execution log includes such metadata, the master data managementmodule 533 of the block chain based data protection system 526 may parsesuch metadata describing the dataset that has been flagged and thecustomized data integration process pursuant to which such a dataset hasbeen flagged from the execution log. The master data management module533 may transmit instructions 505 to the block chain module 534 of theblock chain based data protection system 526 to update metadata trackingblock chains associated with each flagged dataset with the parsedmetadata. For example, the execution log may have flagged the firstdataset with a dataset field name “social” and a dataset field value“123-45-6789,” the second dataset with a dataset field name “SSN” and adataset field value “123-45-6789,” and the third entry indicating athird dataset with a dataset field name “social_security_number” forblock chain tracking.

In such an embodiment, the master data management module 533 maytransmit an instruction 505 to the block chain module 534 to store inthe block chain hyperledger 535 metadata associated with these threedatasets in the execution log in a new metadata tracking block (ormultiple tracking blocks, each containing metadata for one of the threedatasets), and to link that newly created block(s) to an alreadyestablished block or block chain stored in the block chain module 534and associated with the dataset field value “123-45-6789.” For example,the block chain module 534 may create a new metadata tracking blockrecording that a first dataset with a dataset field name “social” and adataset field value “123-45-6789” was read from database 542, a secondentry indicating a second dataset with a dataset field name “SSN” and adataset field value “123-45-6789” was updated at data lake 544, and athird entry indicating a third dataset with a dataset field name“social_security_number” was created within files 546, at the recordedtime of execution of an identified, single customized data integrationprocess. As another example, the block chain module 534 may create afirst new metadata tracking block recording that a first dataset with adataset field name “social” and a dataset field value “123-45-6789” wasread from database 542, create a second new metadata tracking blockrecording that a second entry indicating a second dataset with a datasetfield name “SSN” and a dataset field value “123-45-6789” was updated atdata lake 544, and create a third new metadata tracking block recordingthat a third entry indicating a third dataset with a dataset field name“social_security_number” was created within files 546, at the recordedtime of execution of an identified, single customized data integrationprocess.

In yet another example, the block chain module 534 may create a firstnew metadata tracking block recording that a first dataset with adataset field name “social” and a dataset field value “123-45-6789” wasread from database 542 at the recorded time of a first execution of anidentified, single customized data integration process. The block chainmodule 534 in such an example embodiment may also create a second newmetadata tracking block recording that a second dataset with a datasetfield name “SSN” and a dataset field value “123-45-6789” was updated atdata lake 544 at the recorded time of a second execution of theidentified, single customized data integration process. In addition, theblock chain module 534 in such an example embodiment may also create athird new metadata tracking block recording that a third dataset with adataset field name “social_security_number” was created within files546, at the recorded time of a third execution of the identified, singlecustomized data integration process.

In still another example, the block chain module 534 may create a firstnew metadata tracking block recording that a first dataset with adataset field name “social” and a dataset field value “123-45-6789” wasread from database 542 at the recorded time of execution of a firstidentified customized data integration process. The block chain module534 in such an example embodiment may also create a second new metadatatracking block recording that a second dataset with a dataset field name“SSN” and a dataset field value “123-45-6789” was updated at data lake544 at the recorded time of an execution of a second identifiedcustomized data integration process. In addition, the block chain module534 in such an example embodiment may also create a third new metadatatracking block recording that a third dataset with a dataset field name“social_security_number” was created within files 546, at the recordedtime of an execution of a third identified customized data integrationprocess. In some embodiments, the block chain module 534 may furthercompare the newly created metadata tracking block against other noderegisters operating within the service provider 530, the enterprisesystem 510, or external to both of these. The block chain module 534 maythen store the newly created block(s) within the service provider system530, and update the block chain hyper ledger 535 to reflect addition ofthe newly created block(s) to the pre-existing block chain associatedwith the data field value “123-45-6789.”

In some embodiments, later executions of the same integration processmay result in creation of new metadata tracking blocks associated withthe same dataset field value. Each of these metadata tracking blocks,generated at multiple steps within the execution of a single integrationprocess, or generated pursuant to multiple executions of an integrationprocess, may be linked together to form a block chain describing each ofthe locations at which a single dataset field value has been stored.Such block chains may be searched by dataset field value, or by anothermetadata field value set by the user. In such a way, the block chainassociated with a single dataset field value may track the storagelocations of that dataset over time, even if the dataset field namedescribing that dataset field value has changed over time.

FIG. 6 is a block diagram illustrating a data integration processingmodule for reporting physical storage locations of a dataset field valuepursuant to one or more executed integration processes identified by theuser as potentially containing sensitive personal information,determined based on metadata stored in a block chain associated with thedataset field value according to an embodiment of the presentdisclosure. As described herein, users executing customized dataintegration processes for creation, reading, updating, or deletion ofdatasets containing such potentially sensitive personal information mayrequest a report of known storage locations for a given dataset fieldvalue over time, pursuant to such executed customized data integrationprocesses in embodiments. For example, a block chain based dataprotection system 626 of a service provider in an embodiment may receivea user reporting instruction 601 for a dataset field value in anembodiment. As also described herein, users executing customized dataintegration processes for creation, reading, updating, or deletion ofdatasets containing such potentially sensitive personal information mayrequest deletion of a given dataset field value from one or morelocations at which such a dataset has been stored over time, pursuant tosuch executed customized data integration processes in embodiments. Forexample, a block chain based data protection system 626 of a serviceprovider in an embodiment may receive a user deletion instruction 602for a dataset field value in an embodiment. The user reportinginstruction 601 or the user deletion instruction 602 in such anembodiment may identify the dataset field value by providing a an exactuser-specified dataset field value (e.g., “123-45-6789”), or byproviding a user-specified search term (e.g., “social_security_number”)which may be used to identify a block chain associated with an exactdataset field value (e.g., “123-45-6789”).

Such a user reporting instruction 601 or user deletion instruction 602may be received via the master data management module 633 of the blockchain based data protection system 626, which may then transmit to theblock chain module 634 of the block chain based data protection system626 a request 603 for retrieval of the stored block chain associatedwith the exact user-specified dataset field value or associated with theuser-specified search term. As described herein, the block chain hyperledger 635 in an embodiment may store an association between themetadata tracking block, the user-specified dataset field value, and theone or more user-specified search terms or keys supplied by the userthat may be used to later identify the block chain for the identifieddataset field value. For example, in an embodiment described withreference to FIG. 3A, the user may insert a block chain tracking visualelement 308 in the process flow to track datasets having a dataset fieldvalue “123-45-6789.” In such an example embodiment, the user may use thegraphical visual user interface to further associate block chainscreated pursuant to insertion of the block chain tracking visual element308 into the process flow with user-selected search terms such as“social,” “social_security_number,” or “SSN.” Returning to FIG. 6 , insuch an example embodiment, a block chain recorded in the block chainhyperledger 635 for a dataset having the dataset field value“123-45-6789” may also be associated in the hyperledger 635 with thesearch terms “social,” “social_security_number,” or “SSN.”

In an embodiment, the block chain module 634 of the block chain baseddata protection system 626 may access the block chain hyperledger 635 toretrieve an identification of the block chain storing metadata for theuser-identified dataset field value, or an identification of the blockchain associated with the user-specified search term. In an exampleembodiment, the block chain based data protection system 626 of theservice provider may receive a reporting request 601 or a user deletioninstruction 602 for all datasets having a field value “123-45-6789.” Insuch an embodiment, the master data management module 633 of the blockchain based data protection system 626 may transmit an instruction 603to the block chain module 634 of the block chain based data protectionsystem 626 to retrieve all block chains associated in the block chainhyperledger 635 with a dataset field value “123-45-6789.” The blockchain module 634 in such an embodiment may transmit all block chains 604associated with dataset field value “123-45-6789” back to the masterdata management module 633. Such a block chain in an example embodimentmay include, for example, a first block identifying a dataset having adataset field name “social,” and a dataset field value “123-45-6789,”which was stored at database 642 during execution of a first identifiedcustomized data integration process. In such an embodiment, the blockchain may also contain a second block identifying, for example, adataset having a dataset field name “SSN,” and a dataset field value“123-45-6789,” which was stored at data lake 644 during execution of asecond identified customized data integration process. Such a blockchain in an embodiment may also include, for example, a third blockidentifying a dataset having a dataset field name“social_security_number,” and a dataset field value “123-45-6789,” whichwas stored at files 646 during execution of a third identifiedcustomized data integration process.

In an embodiment, the block chain based data protection system 626 ofthe service provider may receive a user reporting instruction 601 or auser deletion instruction 602 for all datasets associated within a blockchain with one or more of the search term “social_security_number.” Themaster data management module 633 of the block chain based dataprotection system 626 in such an embodiment may transmit an instruction603 to the block chain module 634 of the block chain based dataprotection system 626 to retrieve all block chains associated within theblock chain hyper ledger 635 with the one or more search term“social_security_number.” As described herein, the block chain hyperledger 635 may have associated the dataset field value “123-45-6789”with one or more of these search terms “social,”“social_security_number,” or “SSN.” Thus, the block chain module 634 insuch an embodiment may transmit all block chains 604 associated with thedataset field value “123-45-6789” back to the master data managementmodule 633. In some embodiments, the master data management module 633and block chain module 634 may support Boolean search capabilities,resulting in identification of block chains meeting two or more searchterms, in combination. In such embodiments, the dataset field value maycomprise one of the two or more search terms.

The block chain module 634 in an embodiment may then transmit theidentified block chain 604 (or single block in some circumstances) tothe master data management module 633. In such an embodiment, the masterdata management module 633 may parse the information given within one ormore received block chains 604, to identify address-identified memorylocations at which a user-specified dataset field value or a datasetfield value identified within the block chain has been stored, and togenerate a report 605 detailing such information. For example, themaster data management module 633 in an embodiment may parse thereceived block chain 604 described above, to identify that the datasetfield value “123-45-6789” was stored at database 642 under a datasetfield name “social” during execution of a first identified customizeddata integration process, stored at data lake 644 under a dataset fieldname “SSN,” and stored at files 646 under a dataset field name“social_security_number” during execution of a third identifiedcustomized data integration process.

Such a report 605 may further detail other information given within theblock chain(s) 604 associated with such a dataset field value, andparsed by the master data management module 633. For example, a report605 generated at the master data management module 633 in an embodimentmay identify a dataset field name associated with the identified datasetfield value at each listed address-identified memory location, one ormore integration processes that resulted in the creation, reading,updating, or deletion of the identified dataset field value at or fromthe listed address-identified memory locations, and the times and datesat which such actions occurred.

Thus, the user may specify only a single search term (e.g.,“social_security_number”), and may receive a report on all datasetsstored at the database 642, data lake 644, and files 646 that includethe dataset field value “123-45-6789,” despite the fact that thisdataset field value is stored at the database 642 and the data lake 642under dataset field names other than “social_security_number.” Themaster data management module 605 of the service provider block chainbased data protection system 626 in such an embodiment may transmit thereport 605 for review at the enterprise system/network 610. In such away, the block chain based data protection system in embodiments mayenable users to comply with GDPR reporting requirements by generating areport detailing each of the address-identified memory locations atwhich the user-identified dataset field value has been stored, and thedataset field name associated with that dataset field value at each ofthese address-identified memory locations.

FIG. 7 is a block diagram illustrating a master data management modulefor automatic deletion of a dataset field value identified by the useras potentially containing sensitive personal information, determinedbased on metadata stored in a block chain associated with the datasetfield value from one or more storage locations according to anembodiment of the present disclosure. As described herein, a user mayrequest removal of dataset field values at one or more known storagelocations. For example, if an employee leaves a position with the user,the user may wish to remove all potentially sensitive personalinformation associated with that employee at each address-identifiedmemory location under the control of the user/employer. In someembodiments, the service provider may automatically initiate a deletionprocess for deletion of each of these identified dataset field values,at each location identified within the block chains associated with eachof these identified dataset field values.

As described herein (e.g., with respect to FIG. 6 and incorporated intothe discussion of the system operation described in FIG. 7 ), the blockchain based data protection system 626 of the service provider mayreceive a user deletion request 602 for user-identified dataset fieldvalues, or for dataset field values associated within a stored blockchain with a user-specified search term. In response to a request by themaster data management module 633 of the block chain based dataprotection system 626 in such an embodiment, the block chain module 634of the block chain based data protection system 626 may transmit allblock chains associated the user-specified dataset field value, orassociated with the user-specified search term(s) to the master datamanagement module 633. For example, the master data management module633 in an embodiment may receive all block chains associated within theblock chain hyper ledger 635 with a user-specified dataset field value“123-45-6789,” or with search term “social_security_number.” These blockchains may be temporarily stored at or accessible by the master datamanagement module 633, following generation of a report describingphysical storage locations of datasets associated with these receivedblock chains. Upon receipt of such a user deletion instruction 602 todelete a specifically identified dataset associated with a known blockchain, the master data management module 633 in an embodiment mayreference the block chain associated with this specifically identifieddataset, as received from the block chain module 634, to identify one ormore address-identified memory locations at which the dataset has beenstored, or at which it is currently stored. For example, the master datamanagement module 633 may access a received block chain to determine adataset field value “123-45-6789” was stored at database 642 under adataset field name “social” during execution of a first identifiedcustomized data integration process, stored at data lake 644 under adataset field name “SSN,” and stored at files 646 under a dataset fieldname “social_security_number” during execution of a third identifiedcustomized data integration process.

Turning to FIG. 7 showing the operation of the automatic deletionactivity, upon identification of one or more locations at which auser-specified dataset field value has been stored, the master datamanagement module 733 of the block chain based data protection system726 in an embodiment may initiate an automatic deletion process todelete the user-specified dataset field value from one or more of theselocations. For example, the master data management module 733 of theblock chain based data protection system 726 in an embodiment maytransmit instructions 701 to the data integration process module 731 ofthe integration application management system 732 to generate a deletionprocess for deletion of the datasets having the dataset field value“123-45-6789” identified within the user deletion instruction from oneor more of the locations 742, 744, or 746 at which the identifieddataset is currently stored. Such an instruction 701 may contemplatedeletion of the identified dataset from all known storage locations, orfrom a subset of known storage locations. For example, the user mayidentify, within the user deletion instruction, one or more subsets(e.g., only databases, only data lakes, only files, or only locationsoutside of a specified geographic area) of known storage locations fromwhich the identified dataset should be deleted or all. In response tothe instruction 701, the data integration processing module 731 of theintegration application management system 732 in an embodiment maygenerate a deletion process flow model for such a deletion process. Forexample, the data integration processing module 731 of the integrationapplication management system 732 may generate a deletion process flowmodel such as discussed above with respect to FIG. 3B. The deletion codeinstructions associated with each of the visual elements depicted insuch an embodiment described with respect to FIG. 3B, as well as theruntime engine generated by the data integration process module 731 forexecution of such deletion code instructions may be stored at the dataintegration process module 731 upon automatic creation of such adeletion process flow model. The data integration process module 731 ofthe integration application management system 732 may then transmit theunderlying deletion code instructions and runtime engine 702 to themaster data management module 733 of the block chain based dataprotection system 726 for execution of the deletion process modeled bythe deletion process flow model (e.g., as described with reference toFIG. 3B) by the service provider server/system. In other embodiments,the data integration process module 731 of the integration applicationmanagement system 732 may instead transmit the underlying deletion codeinstructions and runtime engine 706 directly to the enterprisesystem/network 710 or to the enterprise system/network 710 via themaster data management module 733 (not shown) for execution of thedeletion actions by the enterprise system/network 710.

The master data management module 733 of the block chain based dataprotection system 726 in an embodiment may automatically execute thedeletion process at the service provider system/server by executing theruntime engine and deletion code instructions 702 received from the dataintegration process module 731 of the integration application managementsystem 726. Such a deletion process may operate to delete one or moredatasets identified by the enterprise system/network 710 in the userdeletion instruction from one or more address-identified storagelocations 742, 744, or 746 identified as currently storing suchidentified datasets by the master data management module 733 of theblock chain based data protection system 726. For example, the deletionprocess initiated by the master data management module 733 of the blockchain based data protection system 726 and executed by the receivedruntime engine 702 may operate to transmit an instruction 703 to deletethe identified dataset from the database 742, an instruction 704 todelete the identified dataset from the data lake 744, or an instruction705 to delete the identified dataset from the files 746.

In another embodiment, the enterprise system/network 710 in anembodiment may execute the deletion process by executing the runtimeengine and deletion code instructions 706 received from the dataintegration process module 731 or via the master data management module733 of the integration application management system 726. For example,the deletion process initiated at the enterprise system/network 710 andexecuted by the received runtime engine 706 may operate to transmit aninstruction 707 to delete the identified dataset from the database 742,an instruction 708 to delete the identified dataset from the data lake744, or an instruction 709 to delete the identified dataset from thefiles 746. In such a way, the block chain based data protection systemin an embodiment may automatically delete datasets identified by a useras potentially containing sensitive personal information ataddress-identified storage locations recorded as having such sensitivepersonal information, and enable users to comply with reporting andmitigating GDPR requirements, and to ensure proper storage and deletion,where appropriate, of the sensitive personal information. The executionof the deletion action for sensitive personal information at the one ormore address-identified storage locations may be recorded as a block inthe block chain hyperledger 735 via the blockchain module 734 in someembodiments. Thus, the status of the sensitive personal information atvarious address-identified storage locations may be recorded in theimmutable record and reported as needed in some embodiments herein.

FIG. 8 is a flow diagram illustrating a method of creating or updating ablock chain describing physical storage locations for, and one or moredataset field names associated with a dataset field value according toan embodiment of the present disclosure. As described herein, a singledataset field value may receive multiple dataset field names throughoutone or more customized data integration processes, pursuant to which thedata field value is stored at one or more address-identified memorylocations. Embodiments of the present disclosure address this issue bycreating and referencing a block chain tracking physical storagelocations for each dataset field value identified as containingpotentially sensitive personal information, and each dataset field nameassociated therewith at each recorded storage location.

At block 802, a user in an embodiment may insert a block chain visualelement into an integration process flow model. For example, in anembodiment described with reference to FIG. 3A, if a user anticipates amodeled integration process may access, copy, transmit, or otherwisemanipulate a dataset field value likely to include sensitive information(e.g., personal information protected under the GDPR), the user mayinsert a block chain tracking visual element 308 identifying suchdataset field values. In such an embodiment, dataset field values may beidentified based on a search for specific terms within metadataassociated with datasets. Such a user block chain instruction may resultin the generation of a block containing metadata describing theaddress-identified memory location at which the dataset field valuelikely to include sensitive personal information is stored, pursuant toeach execution of the integration process modeled within the processflow of FIG. 3B. Thus, multiple blocks may be generated, with each blockdescribing a single instance in which the identified dataset field valuewas stored at a given address-identified memory location. Each of thesemultiple blocks in an embodiment may be cryptographically linked to oneanother to form a block chain, which may be stored at one of a pluralityof nodes. As described herein, the decentralized, public, cryptographiclinking structure of block chains in an embodiment may provide asubstantially immutable record of each transaction recorded within eachblock. Thus, the block chain created pursuant to a received user blockchain instruction may provide an immutable record of eachaddress-identified memory location at which an identified dataset fieldvalue has been stored pursuant to each execution of the user-modeledcustomized integration process.

As another example, in an embodiment described with reference to FIG. 4, a user may create and edit customized data integration process flowsvia the graphical visual user interface, thus transmitting instructions402 that model the user's integration process flow (including a userblock chain instruction) to a data integration processing module 431maintained and operated by the service provider system/server 430managing the graphical visual user interface. Such instructions 402 maydefine each step of a user-defined data integration process, includinguser block chain instructions to track storage locations for auser-specified dataset that may contain sensitive personal information.These user block chain instructions may identify a dataset field valuethe user believes may include sensitive personal information, and mayalso include one or more search terms or keys that may be used to lateridentify the block chain for the identified dataset field value. Theblock of the blockchains may also include entries recording any updatesthat have occurred at address-identified locations that may containsensitive personal information including, for example, block chainrecords in blocks indicating deletion of sensitive personal informationat such address-identified locations when that has occurred for laterreporting purposes.

The user in an embodiment may choose a dataset field name for blockchain tracking at block 804. For example, in an embodiment describedwith reference to FIG. 3A, upon insertion of the block chain trackingvisual element 308 into the integration flow, a user may be prompted toprovide search terms to be used to identify datasets being integrated bythe modeled process that may contain potentially sensitive personalinformation or to identify such datasets by a specific dataset fieldvalue following a future execution of the modeled customized dataintegration process. The user may further define one or more searchterms that may be used to locate the metadata tracking block chain forthat dataset in the future, via the graphical visual user interface. Forexample, the user may identify a dataset field value “123-45-6789” viathe block chain tracking visual element 308 by directly entering thisvalue, then provide search terms such as “social_security_number,” or“SSN” that may be used in the future to locate the block chain fortracking this dataset field value for a particular dataset value orclass of dataset values depending on the operation being searched.

At block 806, the block chain based data protection system in anembodiment may generate connector code sets and a runtime engine for themodeled customized data integration process and transmit them to anenterprise system. For example, in an embodiment described withreference to FIG. 4 , the data integration processing module 431 mayoperate to generate or customize code instructions (e.g., connector codesets) executable by the enterprise system network 410 to perform thecustomized data integration process modeled by the user via thegraphical user interface. The data integration processing module 431 inan embodiment may transmit machine-executable code instructions 406 forexecuting the modeled customized data integration process and a runtimeengine for later execution thereof to the enterprise system/network 410.Such code instructions 406 may include commands to transmit an executionlog from the user's enterprise network 410 to the service provider 430describing one or more aspects of datasets for which the user hasinitiated block chain tracking pursuant to the customized dataintegration process flow modeled via the graphical user interface.

For example, in an embodiment described with reference to FIG. 3A, theblock chain tracking visual element 308 may be associated with codeinstructions directing creation of an execution log that includesmetadata associated with user-identified datasets. Such metadata mayfurther include the locations at which the dataset is stored pursuant tothe modeled customized data integration process during later executionsthereof, as well as the dataset field names under which such identifieddataset field values are stored at those locations. The codeinstructions may further include a command to transmit the generatedexecution log with such metadata from the remote location at which theintegration is later executed to the service provider managing theintegration process-modeling user interface shown in FIG. 3A.

In other aspects, in an embodiment described with respect to FIG. 4 ,the data integration processing module 431 may transmit instructions 404to create or add blocks to a block chain identifying a dataset fieldvalue for such a dataset, as well as the integration process in whichsuch a dataset will be created, read, updated, or deleted pursuant tothe user instructions 402 to the block chain module 434. The block chainmodule 434 in such an embodiment may then create a new metadata trackingblock identifying the user-identified dataset and add this newly createdblock to an existing block chain, if one exists, which may later receivemore additionally created blocks, following execution of the integrationprocess modeled by the user.

The dataset having the user-specified dataset field name may be created,read, updated, or deleted pursuant to the customized data integrationprocess executed at the enterprise system in an embodiment at block 808.For example, in an embodiment described with reference to FIG. 5 , uponreceipt of the runtime engine and code instructions for execution of theuser-modeled customized data integration process at the enterprisesystem 510, the user may initiate the runtime engine to execute thosecode instructions. An information handling system within the enterprisesystem 510 executing the runtime engine may then establish communicationwith one or more remote server locations or backend applications (e.g.,database 542, data lake 544, or files 546).

Code instructions executed at the enterprise system 510 by such aruntime engine may direct the creation, reading, updating, or deletion(CRUD) of one or more datasets pursuant to a user-modeled customizeddata integration process flow. For example, the enterprise system 510 inan embodiment may execute code instructions 501 of an integrationprocess to read a dataset including the dataset field name “social” andthe dataset field value “123-45-6789” from the database 542, update adataset having a dataset field name “SSN” stored at the data lake 544 toinclude a dataset field value of “123-45-6789,” and to create a datasethaving a dataset field name “social_security_number” stored in files 546to include a dataset field value of “123-45-6789.” Thus, a singlecustomized data integration process may include accessing, storing, orupdating the same dataset field value (e.g., social security number“123-45-6789”) at multiple locations, with each location associating thedataset field value with a different dataset field name (e.g., “social,”“SSN,” or “social_security_number”). In other embodiments, theinstructions 501, 502, and 503 may be transmitted pursuant to threeseparate executions of a single customized data integration process, orpursuant to three separate customized data integration processes, forexample.

At block 810, a metadata block, including metadata for the datasethaving the user-specified dataset field value may be created in anembodiment, transmitted and added to an existing block chain, stored atthe service provider, if one already exists. For example, in anembodiment described with reference to FIG. 5 , following execution ofcode instructions 501, 502, and 503, the enterprise system 510 maygenerate an execution log describing such an execution. The executionlog in such an embodiment may include metadata for the datasets created,read, updated, or deleted pursuant to the code instructions 501, 502,and 503, and may describe the dataset field name and dataset fieldvalues for each dataset involved, and the address-identified memorylocations at which each dataset has been stored. For example, anexecution log in an embodiment may include a first entry indicating afirst dataset with a dataset field name “social” and a dataset fieldvalue “123-45-6789” was read from database 542, a second entryindicating a second dataset with a dataset field name “SSN” was updatedto include dataset field value “123-45-6789” at data lake 544, and athird entry indicating a third dataset with a dataset field name“social_security_number,” and a dataset field value “123-45-6789” wascreated within files 546. The enterprise system 510 in such anembodiment may transmit the execution log 504 to the master datamanagement module 533 managed by the service provider 530.

Upon receipt of the execution log at the service provider 530, themaster data management module 533 may determine whether the executionlog includes metadata for any datasets flagged by the user for blockchain tracking. If the execution log includes such metadata, the masterdata management module 533 may parse such metadata from the executionlog, and transmit instructions 505 to the block chain module 534 tocreate a new metadata tracking block associated with each flaggeddataset within the parsed metadata. For example, the execution log mayhave flagged the first dataset with a dataset field name “social” and adataset field value “123-45-6789,” the second dataset with a datasetfield name “SSN” and a dataset field value “123-45-6789,” and the thirdentry indicating a third dataset with a dataset field name“social_security_number” for block chain tracking. In such anembodiment, the master data management module 533 may transmit aninstruction 505 to the block chain module 534 to store in the blockchain hyperledger 535 metadata associated with these three datasets inthe execution log in a new metadata tracking block, and to link thatnewly created block to an already established block or block chainstored in the block chain hyperledger 535 and associated with thedataset field value “123-45-6789.” The block chain module 534 may thenstore the newly created block within the service provider system 530,and update the block chain hyper ledger 535 to reflect addition of thenewly created block to the pre-existing block chain associated with thedata field value “123-45-6789.”

In some embodiments, later executions of the same integration processmay result in creation of new metadata tracking blocks associated withthe same dataset field value. Each of these metadata tracking blocks,generated at multiple steps within the execution of a single integrationprocess, or generated pursuant to multiple executions of an integrationprocess, may be linked together to form a block chain describing each ofthe locations at which a single dataset field value has been stored, ortransactions involving updating or deleting data at these locations.Such block chains may be searched by dataset field value, or by anothermetadata field value set by the user. In such a way, the block chainassociated with a single dataset field value may track the locations ofthat dataset over time, and states of operation on the stored data, evenif the dataset field name describing that dataset field value haschanged over time. At this point, the flow may end however, the blockchain ledger continues to maintain a record of activities involvingsensitive personal data for tracking purposes as operated on by theintegration.

FIG. 9 is a flow diagram illustrating a method of reporting metadata foror automatically deleting user-identified datasets transmitted accordingto a customized data integration process according to an embodiment ofthe present disclosure. As described herein, users executing customizeddata integration processes for creation, reading, updating, or deletionof datasets containing potentially sensitive personal information mayrequest a report of locations at which a given dataset field value mayhave been stored over time, pursuant to executed, customized dataintegration processes. Such reporting may assist in avoiding ormitigating infringement of the GDPR.

The block chain based data protection system in an embodiment mayreceive a user instruction to display or delete datasets having theuser-specified dataset field value, or meeting user-specified searchterms at block 902. As described herein, users executing customized dataintegration processes for creation, reading, updating, or deletion ofdatasets containing potentially sensitive personal information mayrequest a report of known storage locations for a given dataset fieldvalue over time, pursuant to such executed customized data integrationprocesses in embodiments. As also described herein, a user may furtherrequest removal of such dataset field values at one or more of suchknown storage locations. For example, if an employee leaves a positionwith the user, the user may wish to remove all potentially sensitivepersonal information associated with that employee at eachaddress-identified memory location under the control of theuser/employer. In an embodiment described with reference to FIG. 6 , forexample, a user may transmit a user reporting instruction 601 or a userdeletion instruction 602 from the enterprise system 610 to the masterdata management module 633. As described herein, such a user reportinginstruction 601 or user deletion instruction 602 in such an embodimentmay identify the dataset field value by providing a an exactuser-specified dataset field value (e.g., “123-45-6789”), or byproviding a user-specified search term (e.g., “social_security_number”)which may be used to identify a block chain associated with an exactdataset field value (e.g., “123-45-6789”).

At block 904, the block chain based data protection system in anembodiment may retrieve the block chain associated with theuser-specified dataset field value or the user-specified search terms,as stored in the block chain module. For example, in an embodimentdescribed with reference to FIG. 6 in which the service provider 630receives a user reporting instruction 601 or a user deletion instruction602 for all datasets having a field value “123-45-6789,” the master datamanagement module 633 may transmit an instruction 603 to the block chainmodule 634 to retrieve all block chains associated in the block chainhyperledger 635 with a dataset field value “123-45-6789.” The blockchain module 634 in such an embodiment may transmit all block chains 604associated with dataset field value “123-45-6789” back to the masterdata management module 633.

In another example embodiment in which the service provider 630 receivesa user reporting instruction 601 or a user deletion instruction 602 forall datasets associated with the search term “social_security_number,”the master data management module 633 may transmit an instruction 603 tothe block chain module 634 to retrieve all block chains associatedwithin the block chain hyper ledger 635 with the search term“social_security_number.” The block chain module 634 in such anembodiment may then transmit all block chains 604 associated with thesearch term “social_security_number” back to the master data managementmodule 633. For example, the block chain module 634 may transmit a blockchain 604 containing several blocks describing metadata associated witha dataset field value “123-45-6789” or other social security numbers tothe master data management module 633. Several of the blocks in such ablock chain 604 in such an embodiment may contain metadata describingstorage, updates, or deletion of the dataset field value “123-45-6789”under dataset field names not containing or matching the search term“social_security_number” (e.g., “social,” or “SSN”). In such a way, theuser may identify storage locations and states of sensitive data storedthere for all datasets containing sensitive personal informationdescribed in terms similar to “social_security_number,” by providingonly the single search term “social_security_number.”

At block 906, the block chain based data protection system in anembodiment may determine whether the received user instruction requestsreporting or deletion of a dataset from one or more storage locationsidentified within the retrieved block chain. For example, in anembodiment described with reference to FIG. 6 , a service provider 630in an embodiment may receive a user reporting instruction 601 or a userdeletion instruction 602 for a specifically identified dataset fieldvalue, or for a dataset meeting a user-specified search term in anembodiment. If the received user instruction or request (e.g., 601)requests generation of a report, the method may proceed to block 908 forgeneration of such a report. If the received user instruction or request(e.g., 602) requests deletion of a dataset, the method may proceed toblock 910 for execution of an automated deletion process.

In an embodiment in which a user request for reporting has been receivedat block 906, a report describing metadata stored in the retrieved blockchain, including statuses and all locations at which datasets includingthe user-specified dataset field value or meeting the user-identifiedsearch terms have been stored may be transmitted to the user'senterprise system/network in an embodiment at block 908. For example, inan embodiment described with reference to FIG. 6 , the master datamanagement module 633 may receive block chains 604 matching auser-specified dataset field value or one or more user-specified searchterms. In such an embodiment, the master data management module 633 mayparse the information given within one or more received block chains604, to identify address-identified memory locations at which auser-specified dataset field value or a dataset field value matchinguser-specified search terms has been stored, and to generate a report605 detailing such information. Such a report 605 may further detailother information given within the block chain(s) 604 associated withsuch a dataset field value, and parsed by the master data managementmodule 633. At block 908, the master data management module 633 in suchan embodiment may transmit the report 605 for review at the enterprisesystem/network 610. In such a way, the block chain based data protectionsystem in embodiments may enable users to comply with GDPR requirementsby generating a report detailing each of the address-identified memorylocations at which the user-identified dataset field value has beenstored, and the dataset field name associated with that dataset fieldvalue at each of these address-identified memory locations. For areporting instruction, the method may then end.

For a user deletion instruction at block 906, the block chain based dataprotection system in an embodiment may create an automated deletionprocess flow model for deleting datasets including the user-identifieddataset field value or meeting the user-identified search terms fromstorage locations identified in the retrieved block chain at block 910.For example, in an embodiment described with reference to FIG. 7 , themaster data management module 733 in an embodiment may reference theblock chain associated with a specifically identified dataset, asreceived from the block chain module 734, to identify one or moreaddress-identified memory locations (e.g., database 742, data lake 744,and within the files 746) at which the dataset has been stored, or atwhich it is currently stored and has not been deleted. The master datamanagement module 733 in such an embodiment may transmit instructions701 to the data integration process module 731 to generate a deletionprocess for deletion of the datasets identified within the user deletioninstruction from one or more of the locations 742, 744, or 746 at whichthe identified dataset is currently stored. In response to theinstruction 701, the data integration processing module 731 in anembodiment may generate a deletion process flow model for such adeletion process. For example, the data integration processing module731 may generate a deletion process flow model such as that discussedabove with respect to FIG. 3B. The deletion code instructions associatedwith each of the visual elements depicted in such an embodimentdescribed with respect to FIG. 3B, as well as the runtime enginegenerated by the data integration process module 731 for execution ofsuch deletion code instructions may be stored at the data integrationprocess module 731 upon automatic creation of such a deletion processflow model.

At block 912, the block chain data protection system in an embodimentmay transmit deletion code instructions and runtime engine for executionof the automated deletion process at an enterprise system/network. Forexample, in an embodiment described with reference to FIG. 7 , the dataintegration process module 731 in an embodiment may transmit theunderlying deletion code instructions and runtime engine 706 directly tothe enterprise system/network 710 for execution of the deletion processmodeled by the deletion process flow model (e.g., as described withreference to FIG. 3B) at that location. In other embodiments, the dataintegration process module 731 may transmit the underlying deletion codeinstructions and runtime engine 702 to the master data management module733.

In an embodiment, the runtime engine may be executed at the enterprisesystem/network 710 to perform the deletion process received from thedata integration process module 731. Such a deletion process may operateto delete one or more datasets identified by the enterprisesystem/network 710 in the user deletion instruction from one or morelocations 742, 744, or 746 identified as currently storing suchidentified datasets by the master data management module 733. Forexample, the deletion process initiated by the master data managementmodule 733 and executed by the received runtime engine 706 may operateto transmit an instruction 707 to delete the identified dataset from thedatabase 742, an instruction 708 to delete the identified dataset fromthe data lake 744, or an instruction 709 to delete the identifieddataset from the files 746. In an alternate embodiment in which themaster data management hub 733 automatically executes the runtimeengine, the instructions 703, 704, and 705 may be transmitted to thedatabase 742, data lake 744, or files 746, respectively, from the masterdata management hub 733. In such a way, the block chain based dataprotection system in an embodiment may automatically delete datasetsidentified by a user as potentially containing sensitive personalinformation, and enable users to comply with GDPR requirements bymitigating propagation of sensitive personal data. At this point, theprocess may end.

The blocks of the flow diagrams 8-9 discussed above need not beperformed in any given or specified order. It is contemplated thatadditional blocks, steps, or functions may be added, some blocks, stepsor functions may not be performed, blocks, steps, or functions may occurcontemporaneously, and blocks, steps or functions from one flow diagrammay be performed within another flow diagram. Further, those of skillwill understand that additional blocks or steps, or alternative blocksor steps may occur within the flow diagrams discussed for the algorithmsabove.

Although only a few exemplary embodiments have been described in detailherein, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. Accordingly, all suchmodifications are intended to be included within the scope of theembodiments of the present disclosure as defined in the followingclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents, but also equivalent structures.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover any andall such modifications, enhancements, and other embodiments that fallwithin the scope of the present invention. Thus, to the maximum extentallowed by law, the scope of the present invention is to be determinedby the broadest permissible interpretation of the following claims andtheir equivalents, and shall not be restricted or limited by theforegoing detailed description.

What is claimed is:
 1. An information handling system operating a blockchain based data protection system comprising: a processor executingcode instructions of the block chain based data protection systemreceiving a user block chain instruction to record a firstaddress-identified memory location at which a dataset field valuecontaining sensitive personal information is stored pursuant to acustomized data integration process modeled via a graphical userinterface including blockchain tracking to track the sensitive personalinformation as it is processed through the customized data integrationprocess; the processor creating a block chain associated with thedataset field value containing the sensitive personal information; anetwork interface device receiving an identification of the firstaddress-identified memory location from a remote execution location forthe customized data integration process; the processor creating a firstblock storing the identification of the first address-identified memorylocation within the block chain; the graphical user interface receivinga user reporting instruction to generate a tracking report for thesensitive personal information; the processor generating the trackingreport including the identification of the first address-identifiedmemory location based on the block chain associated with the datasetfield value containing the sensitive personal information; and thenetwork interface device transmitting the tracking report to the remoteexecution location.
 2. The information handling system of claim 1further comprising: the processor executing code instructions of theblock chain based data protection system receiving a user deletioninstruction to delete the dataset field value from the firstaddress-identified memory location; the processor automaticallygenerating a runtime engine and machine executable deletion codeinstructions for deletion of the dataset field value from the firstaddress-identified memory location; and the network interface devicetransmitting the runtime engine and the machine executable deletion codeinstructions for execution at the remote execution location.
 3. Theinformation handling system of claim 2 further comprising: the processorcreating a second block recording deletion of the dataset field valuefrom the first address-identified memory location.
 4. The informationhandling system of claim 1 further comprising: the processor associatingthe block chain with a plurality of dataset field names for the datasetfield value; and the user reporting instruction including an instructionto generate a tracking report for datasets meeting a user-specifiedsearch term included within one or more of the plurality of datasetfield names.
 5. The information handling system of claim 1 furthercomprising: the user reporting instruction including an instruction togenerate a tracking report for datasets including the dataset fieldvalues.
 6. The information handling system of claim 1 furthercomprising: the processor generating code instructions for thecustomized data integration process modeled via the graphical userinterface to store the dataset field value at a plurality ofaddress-identified memory locations, including the firstaddress-identified memory location; the network interface devicereceiving an identification of each of the plurality ofaddress-identified memory locations from a remote execution location forthe customized data integration process; and the processor creating aplurality of blocks within the block chain recording an identificationof one of the plurality of address-identified memory locations.
 7. Theinformation handling system of claim 6 further comprising: the trackingreport including the identification of each of the plurality ofaddress-identified memory locations based on the block chain associatedwith the dataset field value containing sensitive personal information.8. A method of block chain based data protection comprising: receiving,via a block chain based data protection system, a user block chaininstruction to record a first address-identified memory location atwhich a dataset field value containing sensitive personal information isstored pursuant to a customized data integration process modeled via agraphical user interface; creating a block chain associated with thedataset field value containing sensitive personal information, via aprocessor; receiving an identification, via a network interface device,of the first address-identified memory location from a remote executionlocation for the customized data integration process; creating, via theprocessor, a first block storing the identification of the firstaddress-identified memory location within the block chain; receiving,via the block chain based data protection system, a user deletioninstruction to delete the dataset field value from the firstaddress-identified memory location; automatically generating, via theprocessor, a first runtime engine and first machine executable deletioncode instructions for deletion of the dataset field value from the firstaddress-identified memory location; and transmitting, via the networkinterface device, the first runtime engine and the first machineexecutable deletion code instructions for execution at the remoteexecution location.
 9. The method of claim 8 further comprising:receiving, via the block chain based data protection system, a userreporting instruction to generate a tracking report for the datasetfield value; generating the tracking report, via the processor,including the identification of the address-identified memory locationbased on the block chain associated with the dataset field value anddeletion states at the first address-identified memory location; andtransmitting the tracking report to the remote location.
 10. The methodof claim 8 further comprising: associating, via the processor, the blockchain with a plurality of dataset field names for the dataset fieldvalue; and determining one of the plurality of dataset field names meetsa user-specified search term included within the user deletioninstruction.
 11. The method of claim 8 further comprising: determiningthe dataset field value associated with the block chain matches auser-specified dataset field value included within the user deletioninstruction.
 12. The method of claim 8 further comprising: generatingcode instructions for the customized data integration process modeledvia the graphical user interface to store the dataset field value at aplurality of address-identified memory locations, including the firstaddress-identified memory location, via the processor; receiving, viathe network interface device, an identification of each of the pluralityof address-identified memory locations from a remote execution locationfor the customized data integration process; and creating, via theprocessor, a plurality of blocks within the block chain recording anidentification of one of the plurality of address-identified memorylocations within each of the plurality of blocks.
 13. The method ofclaim 12 further comprising: receiving, via the graphical userinterface, a user deletion instruction to delete the dataset fieldvalue; determining the identification of each of the plurality ofaddress-identified memory locations based on the block chain associatedwith the dataset field value; automatically generating a second runtimeengine and second machine executable deletion code instructions fordeletion of the dataset field value from each of the plurality ofaddress-identified memory locations; and transmitting, via the networkinterface device, the second runtime engine and the second machineexecutable deletion code instructions for execution at the remoteexecution location.
 14. The method of claim 8 further comprising:receiving, via the network interface device, notification that thedataset field value has been deleted from each of the plurality ofaddress-identified memory locations; and creating, via the processor, aplurality of blocks recording deletion of the dataset field value fromthe plurality of address-identified memory locations.
 15. An informationhandling system operating a block chain based data protection systemcomprising: a processor executing code instructions of the block chainbased data protection system for receiving a user block chaininstruction to record a plurality of address-identified memory locationsat which a dataset field value containing sensitive personal informationis stored pursuant to a customized data integration process modeled viaa graphical user interface; the processor creating a block chainassociated with the dataset field value containing sensitive personalinformation; a network interface device receiving an identification ofeach of the plurality of address-identified memory locations from aremote execution location for the customized data integration process;the processor creating a plurality of blocks stored within the blockchain; each of the plurality of blocks storing an identification of oneof the plurality of address-identified memory locations; the processorreceiving a first user deletion instruction to delete the dataset fieldvalue from a first address-identified memory location within theplurality of address-identified memory locations; the processorautomatically generating a runtime engine and machine executabledeletion code instructions for deletion of the dataset field value fromthe first address-identified memory location; and the network interfacedevice transmitting the runtime engine and the machine executabledeletion code instructions for execution at the remote executionlocation.
 16. The information handling system of claim 15 furthercomprising: the processor executing code instructions of the block chainbased data protection system receiving a user reporting instruction togenerate a tracking report for the dataset field value; the processorgenerating the tracking report including the identification of each ofthe plurality of address-identified memory locations based on the blockchain associated with the dataset field value containing sensitivepersonal information; and the network interface device transmitting thetracking report to the remote execution location.
 17. The informationhandling system of claim 15 further comprising: the network interfacedevice receiving notification that the dataset field value has beendeleted from the first address-identified memory location; and theprocessor creating a second block recording deletion of the datasetfield value from the first address-identified memory location.
 18. Theinformation handling system of claim 17 wherein the tracking reportfurther includes a report that the dataset field value has been deletedfrom the first address-identified memory location.
 19. The informationhandling system of claim 17 wherein the second block contains a hash ofinformation stored in the first block.
 20. The information handlingsystem of claim 15 further comprising: the processor associating theblock chain with a plurality of dataset field names for the datasetfield value; and the first user deletion instruction including aninstruction to delete datasets meeting a user-specified search termincluded within one or more of the plurality of dataset field names.